Create a new domain for the given environment. After creating the domain, you’ll have to add the required DNS records to your DNS provider. This might be a 2-step process, depending on the verification method used. You can check the required DNS records in the response of this endpoint, and you can verify the domain using the “verify” query parameter in the “Get domain” endpoint.
The Bearer Token generated on the Cloud UI.
The environment identifier
3 - 255root_to_www, www_to_root Whether to enable a wildcard subdomain (*.example.com) for this domain.
false
Whether to allow downtime during domain verification. When true (flexible), the domain can be pointed directly without pre-verification. When false (uninterrupted), TXT-based pre-verification is required to avoid downtime.
true
The Cloudflare integration strategy. "none" uses A records with no Cloudflare integration. "dns" uses CNAME records via Cloudflare DNS only. "dns_proxy" uses CNAME records with Cloudflare's proxy enabled (Orange cloud).
dns_proxy, dns, none "none"
The domain verification method to use. Pre-verification allows domain verification via TXT record before the domain is pointed to the environment. Real-time verification requires the domain to already be pointing to the environment.
pre_verification, real_time "real_time"