This endpoint retrieves all metadata for a specific tenant, including the tenant’s unique ID, name, domain, environment, locality, environment type, and creation date. It is useful for obtaining comprehensive information about a tenant for display in dashboards, auditing, or automated management tasks. The response includes all relevant fields required to identify and manage the tenant programmatically
Documentation Index
Fetch the complete documentation index at: https://docs-dev.auth0-mintlify.app/llms.txt
Use this file to discover all available pages before exploring further.
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
The unique ID of the tenant to retrieve (UUID format) Unique identifier of the tenant
Tenant details retrieved successfully, including tenant ID, name, domain, environment, locality, environment type, and creation date.
Unique identifier of the tenant
The tenant name uniquely identifies a tenant programmatically and within various dashboards, such as Auth0 Dashboard. It can only contain alphanumeric characters, lowercase letters and "-". However, it can't start nor end with "-". If not specified, a tenant name will be auto-generated.
3 - 63^[a-z0-9][-a-z0-9]{1,62}[a-z0-9]$"acme-development-tenant"
The fully qualified domain name of the tenant, which uniquely identifies its domain within the system. The domain is used to define the audience when interacting with the Management API, enabling programmatic management of the tenant’s configuration and resources.
"acme-development-tenant.us.auth0.com"
"acme-development-tenant.acme-dev.auth0app.com"
The name of the cloud environment where the tenant was created
"US-3"
"EU-1"
"acme-dev"
Locality in which the tenant was created
"us"
"eu"
"virginia"
"frankfurt"
The date and time when the tenant was created, formatted in ISO 8601 standard. This timestamp ensures consistency across time zones and systems
Specifies the Environment tag for the tenant created in the Auth0 Public Cloud. It is used to distinguish between development, staging and production environments.
Development and Staging environments are intended for testing and pre-production use, while production is designated for live applications and subject to higher rate limits. Selecting the correct environment type ensures appropriate resource allocation and rate limits
development, production, staging "development"