POST
Verify MFA (step 2 of 2)

Overview

Second and final step of admin login. Present the mfaTicket returned by POST /admin/auth/login together with the current 6-digit TOTP code from the operator’s authenticator app. On success the server issues:
  • an access token — RS256 JWT, scope: 'admin', 15-minute TTL. Required as Bearer on every other admin endpoint.
  • a refresh token — opaque, 7-day TTL, stored hashed in the admin_refresh_tokens collection.
See Admin auth and MFA for why admins get a separate token scope and refresh collection.
No authentication header. The mfaTicket is the credential. Same 10/min/IP burst limiter as /admin/auth/login.

Authentication

None. The mfaTicket authenticates the request.

Path parameters

None.

Query parameters

None.

Request body

Example payload

Response — 200 OK

Error responses

Example error — 401 MFA_INVALID_CODE

See also

curl

Postman

See docs/postman/swappr.postman_collection.json → Admin Auth → MFA verify.