Third-party Access Tokens are issued by Identity Providers after a user authenticates with that provider. Use the Access Tokens to call the API of the third-party provider that issued them. For example, an Access Token issued after authentication to Facebook could be used to call the Facebook Graph API.

The user authenticates with the IdP by making an HTTP GET call to the /api/v2/user/{user-id} endpoint. To call this endpoint you need a Access Tokens for the Management API that includes the read:user_idp_tokens scope. The Access Token for the IdP will be available in the identities array, under the element for the particular connection. For information on how to call an IdP API, see Call an Identity Provider API.

There is no standard way to renew IdP Access Tokens through Auth0. The mechanism for renewing IdP Access Tokens varies for each provider.

For certain identity providers, Auth0 can store a Refresh Token which you can use to obtain a new Access Token for the IdP. Currently this is supported for the following identity providers:

• BitBucket
• Google OAuth 2.0 (you need to pass the parameter access_type=offline when calling the Auth0 /authorize endpoint)
• Any other OAuth 2.0 IdP
• SharePoint
• Azure AD

Get the IdP Refresh Tokens in the same way as Access Tokens, using the /api/v2/user/{user-id} endpoint. The Refresh Tokens will be available in the identities array, under the element for the particular connection.

In general, IdP Access Tokens are passed to the issuing provider and the issuing provider is responsible for validation of the token.

• Access Tokens
• Identity Providers Supported by Auth0
• Access Tokens for the Management API
• Scopes
• Call an Identity Provider API
• Add Scopes/Permissions to Call Identity Provider's APIs