OptionalheadersAdditional headers to include in requests.
OptionaltimeoutThe default maximum time to wait for a response in seconds.
OptionalmaxThe default number of times to retry the request. Defaults to 2.
OptionalfetchProvide a custom fetch implementation. Useful for platforms that don't have a built-in fetch or need a custom implementation.
Optionalinit: RequestInitOptionalinit: RequestInitOptionalloggingConfigure logging for the client.
OptionalauthOverride auth. Pass false to disable, a function returning auth headers, an AuthProvider, or auth options.
Auth0 domain (e.g., 'your-tenant.auth0.com')
OptionalaudienceAPI audience. Defaults to https://{domain}/api/v2/
OptionaltelemetryEnable/disable telemetry. Defaults to true
OptionalclientCustom client information for telemetry
OptionalwithCustom domain Header to use for whitelisted requests. When provided, the Auth0-Custom-Domain header will be added automatically to supported endpoints. This works seamlessly with custom fetchers - both the custom domain logic and your custom fetcher will be applied.
Auth0 application client ID
Private key for signing the client assertion JWT
OptionalclientAlgorithm for signing the client assertion. Defaults to RS256
OptionaluseEnable mTLS for token endpoint calls.
mTLS (RFC 8705) is a transport-layer concern that is independent of the client
authentication method: a client authenticating with private_key_jwt can still present a
TLS client certificate to obtain a certificate-bound access token. This mirrors v6, which
added the mtls. endpoint alias from useMTLS alone regardless of the auth method.
Configuration for client credentials authentication using JWT assertion. Use this for server-to-server authentication with a private key.
Example: Using client assertion