The My Account API is available in Limited Early Access. To request access, contact your Auth0 account manager. To learn more about Auth0’s product release cycle, read Product Release Stages.
Using Auth0 domain vs. custom domainThe My Account API supports using your canonical Auth0 domain or your custom domain, but you must use the same one throughout the entire process, including:
- Getting an access token
- Setting the
audiencevalue - Calling the My Account API endpoint
Activate the My Account API
You can activate the My Account API for your tenant in the :- Navigate to Authentication > APIs.
- Locate the MyAccount API banner.
- Select Activate.

Get an access token
You can get an for the My Account API in the same way you’d get an access token for one of your own APIs.If you’re going to allow the My Account API to perform sensitive operations (such as enrolling an authentication method), we strongly recommend that you use step-up authentication to enforce additional security policies through multi-factor authentication (MFA).
- Call Your API Using the Authorization Code Flow
- Call Your API Using the Authorization Code Flow with PKCE
Audience
The of the My Account API ishttps://{yourDomain}/me/.
Scope
The My Account API supports the following scopes:| Scope | Description |
|---|---|
create:me:authentication-methods | Allows the user to enroll a new authentication method. |
Examples
Universal Login with authorization code flow
Step 1: Request authorization code
Step 2: Exchange code for access token
Embedded login with native passkeys
Step 1: Request login challenge
Step 2: Authenticate existing user
Endpoints
The My Account API functionality is currently limited to Native Passkey Enrollment. Auth0 will add support for more self-service capabilities in the future.
Authentication methods
Enroll an authentication method
Allows the user to enroll a new authentication method (such as a passkey). ENDPOINTPOST https://{yourDomain}/me/authentication-methods
SCOPES
create:me:authentication-methods
BODY PARAMETERS
| Parameter | Data type | Required? | Description |
|---|---|---|---|
type | string | Required | The type of authentication method. Available values: passkey. |
connection | string | Optional | The name of the connection on which to create the new authentication method. |
identity_user_id | string | Optional | The identifier of the current user identity. Used with linked accounts. |
Rate limits
During Early Access, the My Account API is limited at a tenant level to 25 requests per second.Cross-Origin Requests
If you intend to call the My Account API directly from a browser-based application (like a Single Page Application) running on a different domain than your Auth0 tenant, you will encounter browser security policies known as Cross-Origin Resource Sharing (CORS). By default, browsers block these cross-origin requests. To allow your application to successfully make requests to the API, you must add your application’s domain (its “origin”) to your client’s configuration:- Navigate to Dashboard > Applications. Select the application to view.
- Under Cross-Origin Authentication, toggle on Allow Cross-Origin Authentication.
- Locate Allowed Origins (CORS), and enter your application’s origin URL.
- Select Save.
If you do not need to use CORS for your application, ensure that Allow Cross-Origin Authentication is toggled off. Adding your application’s URL to this list tells Auth0 to trust requests from that origin, allowing your client-side application to access the API.