Start a passwordless sign-in challenge in a registered application.
POST/api/v1/auth/challenges
Authorization
No API key or access token is required. This sign-in operation validates the registered application and challenge proof.
Application and challenge validation
Request headers
Content-Typeapplication/json
Encode the request body as JSON.
Request body
applicationIdstring · required
Public identifier for a registered tenant application. Not a secret.
emailstring · required
The enrolled or invited identity’s contact address.
codeChallengestring · required
Base64url SHA-256 digest of a fresh random proof-key verifier.
codeChallengeMethodstring · required
The codeChallengeMethod values for this request.Allowed: S256
Response
202Accepted
The challenge ID and expiry are returned. The response does not reveal whether the identity is enrolled.
Behavior to account for
No API key is used. Application registration does not authenticate a person. Rate limits, proof-key binding, expiry, and single-use verification protect this flow.
Return the same accepted response for known and unknown identities. Send a code only for an enrolled or invited managed identity. Email matching must not attach existing traveler records.
Errors
Authentication failures return 401 or 403. Inaccessible resources return 404. Business and idempotency conflicts return 409. Rate limits return 429 with retry guidance.
We use cookies to understand how the site is used so we can improve it. Analytics stays off until you accept. You can change your choice anytime from the footer. Read ourPrivacy Policy.