Monitor
Sign in
API v1

Authoritative DNS, managed from your code

Host your domains on Quathos Monitor nameservers and manage everything over a simple REST API: create zones, add records, enable DNSSEC and track delegation — all in JSON.

Quickstart API reference

Copy, paste, run

Create your first zone with a single request.

curl -X POST 'https://api.qflaryx.com/v1/orgs/$ORG_ID/zones' \
  -H 'Authorization: Bearer $QFLARYX_KEY' \
  -H 'Content-Type: application/json' \
  -d '{ "name": "example.com" }'

Response: 201 Created · { "name": "example.com", "status": "pending" }

The basics

  • All endpoints live under a single versioned base URL.
  • Requests and responses are JSON (Content-Type: application/json).
  • Every request is authenticated with an API key sent as a Bearer token — see Authentication.
  • Resources are scoped to your organization: paths start with /orgs/{org_id}.
Base URL 
https://api.qflaryx.com/v1
Authentication API keys with the qfx_ prefix, sent as a Bearer token on every request. Zones Create a zone, point your registrar at our nameservers, go live. Records Manage A, AAAA, CNAME, MX, TXT and more inside each zone. DNSSEC Sign your zone online and publish the DS record at your registrar.

When something fails

Every error returns an HTTP status and a JSON body with a detail message explaining what went wrong.

StatusWhen
401Missing or invalid credentials.
403Authenticated, but not allowed (e.g. unverified e-mail, missing role).
404Resource does not exist in your organization.
409Conflict — domain already registered, DNSSEC already enabled.
422Validation failed — invalid record content, CNAME conflict, plan limit.
502The DNS backend rejected the operation — safe to retry.

See the full error reference →

Frequently asked questions

What is a zone?

A zone is a domain (the apex, like example.com) hosted on Quathos Monitor nameservers. You create it via the API, switch the NS records at your registrar, and the zone becomes active once delegation is detected.

How does activation work?

A new zone starts as pending. Point your domain to ns1.qflaryx.com and ns2.qflaryx.com at your registrar; Quathos Monitor re-checks delegation every 5 minutes (or on demand via check-delegation) and flips the zone to active.

Which record types are supported?

A, AAAA, CNAME, MX, TXT, SRV, CAA, NS, PTR and ALIAS. ALIAS gives you CNAME-like behavior at the zone apex, where a real CNAME is not allowed.

Do API keys expire?

Keys are valid until you revoke them from the dashboard. The full secret is shown only once at creation — store it securely and rotate by creating a new key and revoking the old one.

Changes are live

Record changes are pushed to the authoritative nameservers as part of the request — when the API answers 201 or 200, the answer is already being served. Global propagation to resolvers still depends on the record TTL.
Next Quickstart