> ## Documentation Index > Fetch the complete documentation index at: https://auth0.com/llms.txt > Use this file to discover all available pages before exploring further. # List user consents > Retrieve the list of consents for the authenticated user. ## OpenAPI ````yaml docs/oas/myaccount/myaccount-api-oas.json GET /consents openapi: 3.1.0 info: title: My Account version: '1.0' description: >- The Auth0 My Account API provides a dedicated set of endpoints for users to manage their own account information. Customers can use these APIs to build self-service experiences in their applications or progressively add details to a user account. The My Account API operates within the context of the currently logged-in user and can be used directly within user-facing applications. :::tip Using Auth0 domain vs. custom domain The 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 audience value - Calling the My Account API endpoint For more information, read [Custom Domains](https://auth0.com/docs/customize/custom-domains). ::: ## Activate the My Account API You can activate the My Account API for your tenant in the Auth0 Dashboard: 1. Navigate to Authentication > APIs. 2. Locate the MyAccount API banner. 3. Select Activate. ![](https://images.ctfassets.net/cdy7uua7fh8z/DGkDQNIHcegN8vtQyEvF3/a2e98b06867701a66fa1f1b3df1c996b/My_Account_API_-_Activate.png) By default, the My Account API is created with the following application API access policies: `require_client_grant` for user flows `deny_all` for client (machine-to-machine) flows For an application to access the My Account API on the user's behalf, you must explicitly create a client grant for that application, which allows you to define the maximum scopes the application can request. Alternatively, you can change the policy for user access flows to allow_all, which allows any application in your tenant to request any scope from the My Account API. Because the My Account API exposes sensitive information and operations, Auth0 does not recommend using allow_all for user access flows. You should follow a least privilege principle with the My Account API to ensure applications only get access to what they truly need, minimizing potential security risks. The final permissions granted to the application will be determined by the intersection of the scopes allowed by the application API access policy, the Role-Based Access Control (RBAC) permissions assigned to the end user, and any user consent given (if applicable). :::info Supported flows You cannot update the application API policy for client access to the My Account API, which means you cannot access the My Account API using the Client Credentials Flow. ::: To learn more about how to manage application API access policies and their associated client grants, read [Application Access to APIs: Client Grants](https://auth0.com/docs/get-started/applications/application-access-to-apis-client-grants). ## Get an access token You can get an access token for the My Account API in the same way you'd get an access token for one of your own APIs. :::info   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](https://auth0.com/docs/secure/multi-factor-authentication/step-up-authentication) to enforce additional security policies through [multi-factor authentication (MFA)](https://auth0.com/docs/secure/multi-factor-authentication). ::: If you're using Universal Login, read the following articles: - [Call Your API Using the Authorization Code Flow](https://auth0.com/docs/get-started/authentication-and-authorization-flow/authorization-code-flow/call-your-api-using-the-authorization-code-flow) - [Call Your API Using the Authorization Code Flow with PKCE](https://auth0.com/docs/get-started/authentication-and-authorization-flow/authorization-code-flow-with-pkce/call-your-api-using-the-authorization-code-flow-with-pkce) If you're using embedded login, read the following articles: - [Call Your API Using Resource Owner Password Flow](https://auth0.com/docs/get-started/authentication-and-authorization-flow/resource-owner-password-flow/call-your-api-using-resource-owner-password-flow) - [Login Flow with Native Passkeys API](https://auth0.com/docs/native-passkeys-api#login-flow) ## Examples ### Universal Login with authorization code flow **Step 1: Request authorization code** ``` curl --request GET \ --url 'https://{yourDomain}/authorize?response_type=code&client_id={yourClientId}&redirect_uri=%7ByourRedirectUri%7D&scope=create%3Ame%3Aauthentication_methods&offline_access=&audience=https%3A%2F%2F{yourDomain}%2Fme%2F' ``` **Step 2: Exchange code for access token** ``` curl --request POST \ --url 'https://{yourDomain}/oauth/token' \ --header 'content-type: application/json' \ --data '{"grant_type": "authorization_code","client_id": "{yourClientId}","client_secret": "{yourClientSecret}","code": "{yourAuthorizationCode}","redirect_uri": "{yourRedirectUri}","audience": "{yourAudience}","scope": "create:me:authentication_methods","offline_access": ""}' ``` ### Embedded login with native passkeys **Step 1: Request login challenge** ``` curl --request POST \ --url 'https://{yourDomain}/passkey/challenge' \ --header 'content-type: application/json' \ --data '{"client_id": "{yourClientId}"}' ``` **Step 2: Authenticate existing user** ``` curl --request POST \ --url 'https://{yourDomain}/oauth/token' \ --header 'content-type: application/json' \ --data '{ "grant_type": "urn:okta:params:oauth:grant-type:webauthn", "client_id": "{yourClientId}", "scope": "create:me:authentication_methods offline_access", "audience": "https://{yourDomain}/me/", "auth_session": "{sessionIdFromTheFirstRequest}", "authn_response": "{authenticatorResponse}"}' ``` servers: - url: https://{host}/me/v1 variables: host: default: auth0.auth0.com description: Custom or canonical host name security: [] tags: - name: factors description: Factors x-displayName: Factors - name: connected-accounts description: Connected Accounts x-displayName: Connected Accounts - name: authentication-methods description: Authentication Methods x-displayName: Authentication Methods - name: consents description: Consents x-displayName: Consents - name: organizations description: Organizations x-displayName: Organizations - name: profile description: Profile x-displayName: Profile paths: /consents: get: tags: - consents summary: List user consents description: Retrieve the list of consents for the authenticated user. operationId: getConsents parameters: - $ref: '#/components/parameters/HeaderCorrelationId' - $ref: '#/components/parameters/HeaderTraceparent' responses: '200': content: application/json: schema: $ref: '#/components/schemas/ListConsentsResponseContent' description: Successfully retrieved consents headers: x-ratelimit-limit: $ref: '#/components/headers/XRateLimitLimitHeader' x-ratelimit-reset: $ref: '#/components/headers/XRateLimitResetHeader' x-ratelimit-remaining: $ref: '#/components/headers/XRateLimitRemainingHeader' x-correlation-id: $ref: '#/components/headers/CorrelationIdHeader' traceparent: $ref: '#/components/headers/TraceparentHeader' '401': $ref: '#/components/responses/Unauthorized' '403': $ref: '#/components/responses/Forbidden' '429': $ref: '#/components/responses/TooManyRequests' security: - Bearer-DPoP: - read:me:consents x-codeSamples: [] components: parameters: HeaderCorrelationId: in: header name: x-correlation-id required: false schema: type: string x-sdk-ignore: true description: >- 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). HeaderTraceparent: in: header name: traceparent required: false schema: type: string x-sdk-ignore: true description: >- A [W3C Trace Context](https://www.w3.org/TR/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. schemas: ListConsentsResponseContent: type: object properties: consents: type: array description: List of consents for the authenticated user. items: $ref: '#/components/schemas/Consent' required: - consents additionalProperties: false Consent: type: object description: >- A consent record representing user authorization for a specific client and scope. properties: id: type: string description: The unique identifier of the consent. example: cns_abc123def456 client_id: type: string description: The client ID that the consent was granted to. requested_details: $ref: '#/components/schemas/ConsentDetails' created_at: type: string format: date-time description: The date and time when the consent was created. expires_at: type: string format: date-time description: The date and time when the consent expires. challenge: type: string description: >- The MFA challenge associated with this consent when initiated via push notification. Only present when a push notification was associated. required: - id - client_id - requested_details - created_at - expires_at additionalProperties: false ErrorResponse: properties: type: type: string status: type: number title: type: string detail: type: string validation_errors: type: array items: $ref: '#/components/schemas/ValidationError' required: - type - status - title - detail type: object additionalProperties: false ConsentDetails: type: object description: Details of the consent request properties: binding_message: type: string description: >- A human-readable identifier or message intended to be displayed on both the consumption device and the authentication device to interlock them together for the transaction by way of a visual cue for the end-user. audience: type: string description: The audience (API identifier) that the consent was granted for. scope: type: array items: type: string description: The scopes that were requested for this consent. authorization_details: type: array items: $ref: '#/components/schemas/AuthorizationDetailsItem' description: The full authorization details objects associated with this consent. additionalProperties: false ValidationError: type: object properties: detail: type: string field: type: string pointer: type: string source: type: string required: - detail additionalProperties: false AuthorizationDetailsItem: type: object description: >- A single authorization details object as defined by RFC 9396. Only `type` is guaranteed to be present; all remaining fields are specific to the authorization details type, so the object is intentionally open. properties: type: type: string description: The authorization details type identifier, as defined by RFC 9396. additionalProperties: true headers: XRateLimitLimitHeader: required: true description: >- The maximum number of requests permissible during the limit’s window window schema: type: number XRateLimitResetHeader: required: true description: >- The anticipated time (as a UNIX timestamp, in seconds) when the bucket will be replenished schema: type: number XRateLimitRemainingHeader: required: true description: >- The number of remaining requests remaining in the current window until requests are rejected schema: type: number CorrelationIdHeader: required: false description: >- Echoes the validated `x-correlation-id` supplied on the request, or a generated UUID v4 when none was supplied. schema: type: string TraceparentHeader: required: false description: >- A [W3C Trace Context](https://www.w3.org/TR/trace-context/) header echoing the inbound trace ID with a fresh child span ID. schema: type: string RetryAfterHeader: required: true description: The number of seconds the client should wait before making a new request schema: type: number XAuth0ErrorKindHeader: description: >- An indicator that the rate limit exceeded a is global (per tenant) limit. schema: type: string const: global-rate-limit responses: Unauthorized: content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' description: Unauthorized. headers: x-correlation-id: $ref: '#/components/headers/CorrelationIdHeader' traceparent: $ref: '#/components/headers/TraceparentHeader' Forbidden: content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' description: Forbidden. headers: x-correlation-id: $ref: '#/components/headers/CorrelationIdHeader' traceparent: $ref: '#/components/headers/TraceparentHeader' TooManyRequests: content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' description: Too Many Requests. headers: retry-after: $ref: '#/components/headers/RetryAfterHeader' x-ratelimit-limit: $ref: '#/components/headers/XRateLimitLimitHeader' x-ratelimit-reset: $ref: '#/components/headers/XRateLimitResetHeader' x-ratelimit-remaining: $ref: '#/components/headers/XRateLimitRemainingHeader' x-auth0-error-kind: $ref: '#/components/headers/XAuth0ErrorKindHeader' x-correlation-id: $ref: '#/components/headers/CorrelationIdHeader' traceparent: $ref: '#/components/headers/TraceparentHeader' securitySchemes: Bearer-DPoP: type: http scheme: bearer description: Bearer and DPoP tokens are supported depending on the API configuration ````