Monitor
Sign in

Quickstart

From an API key to a record resolving on the public internet. You'll create a zone, delegate your domain to the Quathos Monitor nameservers and publish an A record.

1. Create your account and organization

Sign up in the dashboard and verify your e-mail. Every account gets an organization — all zones, records and API keys belong to it, and its numeric id appears in every API path as {org_id}.

E-mail verification required

The API refuses to create zones until your e-mail is verified — you'll get a 403 otherwise.

2. Create an API key

In the dashboard, go to API Keys (/painel/tokens) and create a key. The full secret starts with qfx_ and is shown only once — copy it now. See Authentication for scopes and details.

Terminal 
export QFLARYX_KEY="qfx_1a2b3c4d_..."
export ORG_ID="7"
export BASE="https://api.qflaryx.com/v1"

3. Create the zone

Register your apex domain. The zone is created on the Quathos Monitor nameservers immediately and starts as pending until delegation is detected.

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

4. Get the setup instructions

The setup endpoint shows the nameservers assigned to your zone and what the public DNS currently sees for your domain.

curl -s "$BASE/orgs/$ORG_ID/zones/42/setup" \
  -H "Authorization: Bearer $QFLARYX_KEY"

5. Switch nameservers at your registrar

At your domain registrar, replace the current NS entries with the assigned ones:

  • Review your zone's records first, so nothing goes dark during the switch.
  • If DNSSEC is enabled at your old provider, disable it at the registrar before switching.
  • Replace the nameservers with ns1.qflaryx.com and ns2.qflaryx.com.
  • Wait for propagation — minutes up to 24h. Quathos Monitor re-checks every 5 minutes.

6. Check the delegation

Don't want to wait for the automatic check? Trigger one on demand. When all observed NS point to Quathos Monitor, the zone flips to active (and you get an e-mail).

curl -s -X POST "$BASE/orgs/$ORG_ID/zones/42/check-delegation" \
  -H "Authorization: Bearer $QFLARYX_KEY"

7. Create a record

Use a relative name (www), @ for the apex, or the full FQDN. The change is pushed to the nameservers as part of the request.

curl -s -X POST "$BASE/orgs/$ORG_ID/zones/42/records" \
  -H "Authorization: Bearer $QFLARYX_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "www",
    "type": "A",
    "content": "203.0.113.10",
    "ttl": 3600
  }'

8. Verify with dig

Query the Quathos Monitor nameserver directly — the answer is live even before delegation finishes:

Terminal 
dig +short www.example.com A @ns1.qflaryx.com
# 203.0.113.10

Next steps

Previous Introduction Next Kubernetes