Run the verification process on a custom domain.
Note: Check the status field to see its verification status. Once verification is complete, it may take up to 10 minutes before the custom domain can start accepting requests.
For self_managed_certs, when the custom domain is verified for the first time, the response will also include the cname_api_key which you will need to configure your proxy. This key must be kept secret, and is used to validate the proxy requests.
Learn more about verifying custom domains that use Auth0 Managed certificates. Learn more about verifying custom domains that use Self Managed certificates.
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
ID of the custom domain to verify.
Custom domain successfully verified.
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 CNAME API key header.
Intermediate address.
Domain verification settings.
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.