API reference
All operations are sourced from the contract and enriched with request and response examples.
DNS
DNSSEC
curl --request POST \
--url 'https://api.regfish.com/dns/rr' \
--header 'content-type: application/json' \
--header 'x-api-key: YOUR_API_KEY' \
--data '
{
"type": "A",
"name": "custom.example.com",
"data": "123.123.123.123",
"ttl": 60
}
'curl --request PATCH \
--url 'https://api.regfish.com/dns/rr' \
--header 'content-type: application/json' \
--header 'x-api-key: YOUR_API_KEY' \
--data '
{
"type": "A",
"name": "custom.example.com",
"data": "12.12.12.13",
"ttl": 120
}
'curl --request GET \
--url 'https://api.regfish.com/dns/example.com/rr' \
--header 'x-api-key: YOUR_API_KEY'curl --request DELETE \
--url 'https://api.regfish.com/dns/rr/5659983' \
--header 'x-api-key: YOUR_API_KEY'DNS belongs in the workflow. Our open source integrations for zone management, record automation, and ACME DNS challenges support both internal services and our hosting platform. Regfish gives you a capable API plus libraries and tools that help automate DNS changes cleanly:
Integrations for projects such as libdns, caddy-dns (for Caddy and other DNS workflows), lexicon as well as go-acme/lego bring DNS automation into real deployments, from zone sync to challenge delegation.