Create a domain's DNS record in the team's Cloudflare account, when one of its connected zones covers the hostname: an A record to the cluster's public IP, with the comment "Made by Pyo ()". Pyo never overwrites a record. When another A, AAAA or CNAME record has the name, status is "conflict" and existing lists them. Send it again with replace to delete those and create Pyo's (team owners and admins). status "exists" means it already points there. With proxied, Cloudflare proxies it once the domain's certificate is issued.
API key access: full.
apiKeyAuthorizationBearer <pyo_…>An API key from the dashboard's API keys page: Authorization: Bearer pyo_…. Keys can expire, and an expired one gets a 401.
application/jsonCreate a domain's DNS record in the team's Cloudflare account, when one of its connected zones covers the hostname: an A record to the cluster's public IP, with the comment "Made by Pyo ()". Pyo never overwrites a record. When another A, AAAA or CNAME record has the name, status is "conflict" and existing lists them. Send it again with replace to delete those and create Pyo's (team owners and admins). status "exists" means it already points there. With proxied, Cloudflare proxies it once the domain's certificate is issued.
API key access: full.
op*"createDnsRecord""createDnsRecord"serviceId*stringdomainId*stringproxied?booleanProxied by Cloudflare. Off by default.
replace?booleanReplace the records in the way.
Done. Always ok: true, and some operations add more, such as a new API key or a join command. A warning comes with a change that went through but won't fully take effect yet, such as more replicas than the servers have room for.
application/jsoncurl -X POST 'https://your-pyo.example.com/api/v1/ops' \
-H 'Content-Type: application/json' \
-d '{
"domainId": "dom_8kq2x7ad",
"op": "createDnsRecord",
"serviceId": "svc_8kq2x7ad"
}'{}