Create a new custom domain.
Note: The custom domain will need to be verified before it will accept requests.
Optional attributes that can be updated:
TLS Policies:
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Domain name.
^(([a-zA-Z0-9]|[a-zA-Z0-9][a-zA-Z0-9-]*[a-zA-Z0-9])\.)*([A-Za-z0-9]|[A-Za-z0-9][A-Za-z0-9-]*[A-Za-z0-9])$Custom domain provisioning type. Must be auth0_managed_certs or self_managed_certs.
auth0_managed_certs, self_managed_certs Custom domain verification method. Must be txt.
txt Custom domain TLS policy. Must be recommended, includes TLS 1.2.
recommended The HTTP header to fetch the client's IP address
true-client-ip, cf-connecting-ip, x-forwarded-for, x-azure-clientip, Domain metadata associated with the custom domain, in the form of an object with string values (max 255 chars). Maximum of 10 domain metadata properties allowed.
Relying Party ID (rpId) to be used for Passkeys on this custom domain. If not provided, the full domain will be used.
255Custom domain successfully created (verification is pending).
ID of the custom domain.
Domain name.
Whether this is a primary domain (true) or not (false).
Custom domain configuration status. Can be failed, pending_verification, or ready.
pending_verification, ready, failed Custom domain provisioning type. Can be auth0_managed_certs or self_managed_certs.
auth0_managed_certs, self_managed_certs Domain verification settings.
Whether this is the default custom domain (true) or not (false).
The HTTP header to fetch the client's IP address
The TLS version policy
Domain metadata associated with the custom domain, in the form of an object with string values (max 255 chars). Maximum of 10 domain metadata properties allowed.
Certificate information. This object is relevant only for Custom Domains with Auth0-Managed Certificates.
Relying Party ID (rpId) to be used for Passkeys on this custom domain. If not present, the full domain will be used.