Start the enrollment of a supported authentication method.
Start the enrollment of a supported authentication method.
Authorizations
Bearer and DPoP tokens are supported depending on the API configuration
Headers
A client-provided unique identifier for a single operation, used to correlate the request across Auth0 systems. The value is surfaced under references.correlation_id in tenant logs and echoed back on the response's x-correlation-id header. Invalid or oversized values are silently dropped and replaced by a generated UUID v4. Avoid including personally identifiable information (PII).
A W3C Trace Context header used to correlate the request across distributed traces. When supplied, the inbound trace is continued and a fresh child span is echoed back on the response's traceparent header; the trace ID is also surfaced under references.trace_id in tenant logs. Malformed values are ignored.
Specifies the language used for localized content generated while handling the request (such as OTP email or SMS messages), using one of the tenant's configured Supported Languages.
Body
- passkey
- totp
- push-notification
- recovery-code
- email
- phone
- password
Request content for creating an authentication method
Authentication method type (factor)
"passkey"Name of the database connection
1 - 128^[a-zA-Z0-9-]+$Identity provider user ID
1 - 255^\S+$When enabled, Auth0 includes the user's existing credentials in the excludeCredentials field during passkey enrollment. This prevents users from accidentally registering multiple passkeys from the same authenticator, reducing credential clutter and avoiding confusion at sign-in.
Response
Enrollment started
- Passkey enrollment information
- WebAuthn enrollment information
- Email/Phone enrollment information
- TOTP/Push enrollment information
- Recovery Code enrollment information
- Password enrollment information