Pin an RRset to values the customer DECLARES rather than to values we observed.

POST

/dns/record-monitor/{monitor_id}/baseline/declare

curl --request POST \
  --url https://api.siteqwality.com/dns/record-monitor/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0/baseline/declare \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '{ "name": "example", "record_type": "example", "rdata": [ "example" ] }'

• Production

This is what makes the feature useful BEFORE a migration instead of only after one: “these are my four nameservers, tell me if the zone ever says anything else.” Same table, different source, no new mechanism.

Authorizations

• bearer_auth

Parameters

Path Parameters

monitor_id

required

string format: uuid

DNS monitor identifier

Request Body ^required

Media type application/json

What a customer may pin without us having observed it.

source = user_declared. This is what makes the feature useful BEFORE a migration instead of only after one.

object

name

required

string

record_type

required

string

rdata

required

Array<string>

Example ^generated

{
  "name": "example",
  "record_type": "example",
  "rdata": [
    "example"
  ]
}

Responses

200

The declared baseline

Media type application/json

One baseline as the api returns it.

object

id

required

string format: uuid

monitor_id

required

string format: uuid

name

required

string

record_type

required

string

rdata

required

Array<string>

rdata_hash

required

Hex-encoded sha256 of the canonical RRset. This is the value an accept request must echo back, which is what makes acceptance non-racy.

string

rotating

required

boolean

rotating_reason

string | null

ttl

Display only. Never a diff input: a TTL change is an operational fact, not a security one.

integer | null format: int32

source

required

string

established_at

required

string format: date-time

accepted_at

string | null format: date-time

Example ^generated

{
  "id": "2489E9AD-2EE2-8E00-8EC9-32D5F69181C0",
  "monitor_id": "2489E9AD-2EE2-8E00-8EC9-32D5F69181C0",
  "name": "example",
  "record_type": "example",
  "rdata": [
    "example"
  ],
  "rdata_hash": "example",
  "rotating": true,
  "rotating_reason": "example",
  "ttl": 1,
  "source": "example",
  "established_at": "2026-04-15T12:00:00Z",
  "accepted_at": "2026-04-15T12:00:00Z"
}

400

Invalid request body

401

Missing or invalid authentication

404

DNS monitor not found

500

Internal server error