Login with MFA

Authenticates a user who has completed MFA enrolment, and returns the credentials used by every other endpoint. Send the username and password issued during onboarding together with a current TOTP code generated from the secret registered via POST /mfa/enable. A user who has not enrolled receives 403 here until they do.

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Body Params
string
required

The username issued to the user by AUDD during onboarding.

string
required

The password issued to the user by AUDD during onboarding. Users cannot change their own password.

string
required
^[0-9]{6}$

A current 6-digit TOTP code generated from the secret registered via POST /mfa/enable.

Headers
string
required

Your environment API key, sent raw with no "Bearer" prefix. The token this call returns is what you send as "Bearer " on the business endpoints; it is not used here.

Responses

400

Invalid request. Returned when the Authorization header is absent, when a required body field is missing, or when mfaCode is not exactly six digits. Field errors return {"message":"","errors":[""]}; a malformed JSON body returns a plain-text reason instead of JSON.

401

Authorization header present but empty, or rejected by the identity provider.

403

MFA is not enabled for this user. The credentials were accepted but no authenticator is registered, so the user must complete POST /mfa/enable first.

404

The username or password was not accepted. The identity provider does not distinguish an unknown user from a wrong password, and the passed-through body carries no detail.

421

The mfaCode was six well-formed digits but did not match the user's registered authenticator, passed through from the identity provider. Retry with a freshly generated code; if it keeps failing, check the client clock for drift.

Language
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json