Verify MFA
Completes a sign-in that stopped at the second factor.
posthttps://api.integrable.cloud/api/auth/mfa/verify
- Authentication
- None
- Retries
- Idempotency-Key
- Body
- application/json
- Version
- 2026-09-03
Rate limited per account and per address, the same two-sided limit login itself applies and for the same reason: per-address alone lets an attacker work through a list of accounts, per-account alone lets a botnet spread across addresses.
A recovery code is accepted here as well as an authenticator code. The response says which was used, because somebody who has just spent one of ten needs to know now rather than at zero.
Headers#
Request body#
Responses#
Errors#
Failures use one envelope on every endpoint, described in Retries, versioning and limits. The codes you are most likely to meet here:
validation_error· 422 — The payload was well-formed JSON but failed schema validation.idempotency_key_reused· 422 — This `Idempotency-Key` was used before, for a request with a different body.rate_limited· 429 — Too many requests in the current window. The limit is per workspace, and some endpoints add a per-agent limit on top.
More Auth endpoints#
Something unclear or missing? Tell us and we’ll fix it.