Custom Hostnames
custom_hostnames
Methods
Add a new custom hostname and request that an SSL certificate be issued for it. One of three validation methods—http, txt, email—should be used, with 'http' recommended if the CNAME is already in place (or will be soon). Specifying 'email' will send an email to the WHOIS contacts on file for the base domain plus hostmaster, postmaster, webmaster, admin, administrator. If http is used and the domain is not already pointing to the Managed CNAME host, the PATCH method must be used once it is (to complete validation).
Delete Custom Hostname (and any issued SSL certificates)
Modify SSL configuration for a custom hostname. When sent with SSL config that matches existing config, used to indicate that hostname should pass domain control validation (DCV). Can also be used to change validation type, e.g., from 'http' to 'email'.
The previous authorization scheme for interacting with the Cloudflare API, used in conjunction with a Global API key.
Example: X-Auth-Email: user@example.com
The previous authorization scheme for interacting with the Cloudflare API. When possible, use API tokens instead of Global API keys.
Example: X-Auth-Key: 144c9defac04969c7bfad8efaa8ea194
SSL and Certificates Write
Identifier
Identifier
Whether the API call was successful
Custom Hostname Details
List, search, sort, and filter all of your custom hostnames.
Domain types
Fallback Origin
custom_hostnames.fallback_origin
Methods
Delete Fallback Origin for Custom Hostnames
Get Fallback Origin for Custom Hostnames
Update Fallback Origin for Custom Hostnames