API v1 is legacy:
it's read-only and kept for existing integrations. For new integrations, use API v2: see the DNS Check API.
API v1 is DNS Check's original API, at https://www.dnscheck.co/api/v1. It reads the pass/fail status of your record groups and the DNS records in them, which is how the Nagios and Pingdom integrations work. API v2 replaced it: in addition to reading status, v2 can create, change, and delete record groups and DNS records, check DNS records on demand, import and export zone files, and follow every status change through an event feed.
To move an integration from v1 to v2, change the requests and fields below.
How v2 Differs from v1
| Change | v1 | v2 |
|---|---|---|
| Authentication | ?api_key=KEY or Authorization: Bearer KEY |
Authorization: Bearer KEY only |
| List record groups | GET /api/v1/groups/all |
GET /api/v2/record-groups |
| Read a record group | GET /api/v1/groups/{uuid} |
GET /api/v2/record-groups/{id} (the same UUID) |
| List a group's DNS records | GET /api/v1/groups/{uuid}/all |
GET /api/v2/record-groups/{id}/dns-records |
| Read a DNS record | GET /api/v1/groups/{uuid}/{record_id} |
GET /api/v2/dns-records/{id}, where id is the record's UUID rather than its number. To find it, list the group's DNS records in v2: each one's web_url ends in its number. |
| Response format | Responses wrapped in {"group": ...} or {"dns_records": [...]} |
A resource as itself, and lists as {"data": [...], "next_cursor": ..., "has_more": ...} |
| Record type field | record_type |
type |
| Value field | value, a string, with a load balancer record's values comma-separated |
values, an array of strings |
| Errors | A string, or a hash keyed by field | Problem Details with a stable code |