Verify an email code for a directory password migration fallback or recovery transaction and create a session.
curl --request POST \ --url https://auth.example.com/api/auth/directory-password/migration/email-code/verify \ --header 'Content-Type: application/json' \ --data '{ "transaction_id": "damt_email_123", "transaction_token": "migration-email-token", "challenge_id": "challenge_123", "code": "123456" }'Works only where the tenant allows email code for login (authentication-methods.email_otp.login_enabled, off unless turned on). This is decided first, before the transaction or the code is consumed and before any session is created: 403 access_denied (error_code AR050006) when it is off, 503 temporarily_unavailable when the tenant settings cannot be read.
Request Body required
Section titled “Request Body required ”object
Example
{ "transaction_id": "damt_email_123", "transaction_token": "migration-email-token", "challenge_id": "challenge_123", "code": "123456"}Responses
Section titled “ Responses ”Successful JSON response.
object
object
object
object
object
False when the campaign does not offer the email code, or when the tenant has email code for login off (authentication-methods.email_otp.login_enabled) or its settings cannot be read.
object
object
Example
{ "ok": true, "expires_in": 86400, "session": { "userId": "user_123", "createdAt": 1770000000000, "expiresAt": 1770086400000, "authTime": 1770000000, "acr": "urn:mace:incommon:iap:bronze", "amr": [ "pwd", "directory" ] }, "user": { "id": "user_123", "email": "user@example.com", "name": "Example User" }}Successful response. The representation can be JSON, HTML, or a redirect.
Successful response. The representation can be JSON, HTML, or a redirect.
Successful response. The representation can be JSON, HTML, or a redirect.
Successful response. The representation can be JSON, HTML, or a redirect.