GET /v1/domains/{domainId}/dns/records

Pagpapatotoo

Magpadala ng API key bilang isang bearer token. Kailangang taglayin ng key ang pahintulot na sites.view; ang key na wala nito ay tatanggihan gamit ang 403, hindi 404.

Ang endpoint na ito ay hindi nangangailangan ng id ng organisasyon. Natutukoy na ng iyong key ang organisasyong kinabibilangan nito, at nakatuon ang tugon dito.

Subukan ito

Palitan ang anuman sa loob ng mga panaklong na may anggulo ng iyong sariling mga halaga, at ang placeholder ng key na may key mula sa iyong dashboard.

curl -X GET https://api.zinndigital.com/v1/domains/{domainId}/dns/records \
  -H "Authorization: Bearer zdk_live_…"

Nakalagda? Ang API console sa iyong dashboard ay awtomatikong naglalagay ng iyong tunay na ID ng organisasyon at sariling susi, at pinapatakbo ang kahilingan laban sa live na API upang makita mo ang aktwal na tugon. Buksan ang endpoint na ito sa console ng API

Mga Detalye

The resource records in the domain's hosted authoritative zone. Requires `sites.view`, RLS-scoped. **Footprint-Free (PBN) line:** the A/AAAA records publish the shared fleet IP and are hidden entirely from this line (they are platform-managed) — the returned set never contains them (register #93). **Paginated (issue #466).** Keyset cursor over `(name, type, value, id)`, default page size 50, hard maximum 200. Filtering by product line happens **before** pagination, so a hidden record can never surface on a later page. A client must follow `page.next_cursor` until `page.has_more` is false; reading only the first page reads only the first page. **Two different 404s, and a client MUST branch on the `code` rather than the status.** `NOT_FOUND` is the ordinary miss — no such domain, or not in your scope. `DNS_NOT_HOSTED` means the domain exists and is yours, but its nameservers point at another DNS provider, so there is no zone here to read. The second is **permanent until the customer re-delegates** and retrying can never succeed; on a Footprint-Free estate, where most names are registered elsewhere and merely pointed at us, it is the normal answer for most domains rather than an edge case. Both carry the identical message, deliberately, so that a caller who may not see the domain cannot tell the two apart by wording.

Mga Parameter

Tugon

Mga error na maibabalik ng endpoint na ito

401 · 403 · 404 · 429 · 502 · 503