List a domain's DNS records
The DNS records of a domain registered through Cloady in this workspace, or of an application's own address under cloady.io (`<app>-<hash>-<workspace>.cloady.io`, as its endpoints show it). A registration starts with A and AAAA records for the domain and `*` pointing at Cloady; an address starts with none, since a wildcard serves it. Records with `managed` set are Cloady's: they keep the domain or address pointing at your applications and can't be changed or deleted. Answers 409 when a registered domain uses its own nameservers, whose records live there.
Authorization
cloady Personal API token (cldy_…)
In: header
Path Parameters
Response Body
application/json
application/json
application/json
application/json
application/json
application/json
curl -X GET "https://example.com/api/workspaces/string/domains/string/records"{ "records": [ { "id": "string", "name": "string", "type": "string", "content": "string", "ttl": -9007199254740991, "prio": -9007199254740991, "managed": true } ]}List all domains in workspace GET
Every custom domain the workspace's applications serve, and every domain registered through Cloady, with its renewal details, whether or not an application serves it.
Add a DNS record POST
Adds a record to a domain registered through Cloady in this workspace, or under an application's cloady.io address. On a registered domain, A, AAAA, ALIAS and CNAME records on the domain itself and on `*` are Cloady's. Under an address, records go on a name below it, like `mail` or `_verify`, and ALIAS, CAA and NS aren't allowed; the first one also gives the address itself a CNAME to Cloady, because a name with records below it no longer matches the wildcard. Records reach the internet within the TTL; a record the registrar refuses, such as a CNAME beside other records on the same name, answers 400 with its reason. Needs the developer role.