Auth API reference

Auth API · Consumer-Mfa

post/{app_slug}/v1/me/mfa/step-upAuth

Bump this session's MFA recency

Verify a fresh code (TOTP, emailed via `/step-up/send-code`, or recovery) against any enabled factor on the account, and update the session's `auth_methods` + `mfa_at`. Call `/auth/refresh` after this to mint a token whose claims reflect the new state. Customers reading `mfa_at` from access tokens to gate sensitive actions should require a `/step-up` + refresh cycle when the timestamp is older than their policy window. 5 consecutive wrong codes lock step-up on this session for 15 minutes.

Path parameters

app_slug*string

Slug of the app.

Request body

codestring

TOTP or emailed code (6 digits) OR a recovery code (16 hex chars, hyphenated or not). Emailed codes are requested via `/me/mfa/step-up/send-code` first. Omit when submitting `credential` instead.

Example: "123456"

credentialobject

Passkey step-up: the `PublicKeyCredential` returned by `navigator.credentials.get()` against the options from `/me/mfa/step-up/webauthn/options`. Mutually exclusive with `code`.

Response · 200

amr*array

Authentication methods now recorded on the session (RFC 8176 `amr` values, e.g. `pwd`, `otp`, `webauthn`).

Example: ["pwd","webauthn"]

mfa_at*string · date-time

When the second factor was verified on this session (ISO 8601).

Example

Request

POST https://api.auth.productcraft.co/{app_slug}/v1/me/mfa/step-up
Authorization: Bearer YOUR_TOKEN
Content-Type: application/json

{
  "code": "123456",
  "credential": {}
}

Response

{
  "amr": [
    "pwd",
    "webauthn"
  ],
  "mfa_at": "2026-01-01T00:00:00.000Z"
}