For applications using the client_credentials flow, API access is typically performed in the context of a specific tenant (customer). This means that a tenant_id must normally be included in the token request to indicate which tenant’s data the application should access.
The tenant_id parameter is a non-standard extension to the OAuth 2.0 specification. Because of this:
Not all OAuth clients or libraries support sending it
Some tools and integrations make it difficult or impossible to include custom parameters in token requests
The Default Tenant feature addresses this limitation by allowing you to configure a predefined tenant directly on the application.
When a Default Tenant is set:
The application will automatically use the configured tenant context
The
tenant_idparameter no longer needs to be sent in token requestsToken requests become simpler and more compatible with standard OAuth clients
This is especially useful for:
Single-tenant integrations
Backend services with a fixed customer context
Environments where OAuth clients cannot send custom parameters
How to configure a Default Tenant
If your Application has been assigned Tenant(s), follow these steps in the Developer Portal:
Go to My Applications
Select your application
Go to Integrations in the left-menu
Select Customers tab
Click “Set default tenant”
Choose the Tenant you want to set as default
Confirm the Default Tenant
Note that if your Application has not been assigned any Tenant, this will not be available for you.
Set a Default Tenant from the list of Tenants available to your Application.
Now you can do a Client Credentials token request without specifying the Tenant ID parameter.