connections
GET /v1/registrar-domains
The domains in the organization's linked registrar accounts.
प्रमाणीकरण
बेरर टोकन म्हणून API की पाठवा. की मध्ये sites.view परवानगी असणे आवश्यक आहे; ती नसलेली की 404 ऐवजी 403 सह नाकारली जाते.
या एंडपॉइंटला कोणतीही संस्था आयडी (organisation id) लागत नाही. तुमची की (key) आधीच ती कोणत्या संस्थेशी संबंधित आहे हे ओळखते आणि प्रतिसाद त्यानुसार मर्यादित केला जातो.
प्रयत्न करा
कोनसांस्कृतिक कंसात (<>) असलेली कोणतीही गोष्ट तुमच्या स्वतःच्या मूल्यांनी बदला आणि key प्लेसहोल्डरला तुमच्या डॅशबोर्डवरील किने बदला.
curl -X GET https://api.zinndigital.com/v1/registrar-domains \
-H "Authorization: Bearer zdk_live_…"साइन इन केलेले आहे? तुमच्या डॅशबोर्डमधील API कन्सोल तुमची खरी संस्था आयडी आणि तुमची स्वतःची की आपोआप भरतो आणि लाइव्ह API विरुद्ध विनंती कार्यान्वित करतो जेणेकरून तुम्हाला वास्तविक प्रतिसाद पाहता येईल. एपी कन्सोलमध्ये हा एंडपॉइंट उघडा
तपशील
Everything we can see in the GoDaddy, Namecheap or Porkbun accounts the customer has connected, with what we last observed about each name and what — if anything — they need to do about it. ⛔ These are not Domain resources and the two must not be conflated. A Domain is a name the platform is responsible for: we sell it, we renew it, a workflow drives every transition. A row here is a name registered somewhere we did not sell it, whose renewal and ownership are entirely the customer's — we may read it and we may point it at a site, and that is the whole surface. matched_domain_id is the one place they meet, set when a Domain for the same name exists in the same organization. ⛔ nameservers is null when we have never read the delegation — never [], which would say the domain is delegated nowhere. Two of the three registrars' account listings do not carry nameservers at all, so null is the ordinary state of a freshly imported row. ⛔ state is our verdict (is there anything to tell you?) and registrar_status is the vendor's own word, carried through verbatim and unmapped. They answer different questions and a client must not render one as the other: three registrars use three vocabularies, and deciding what AWAITING_VERIFICATION "really" means is not a decision this API takes on a screen whose job is to show the customer what their registrar says. accounts is served beside the domains because a connected account holding zero domains is a state the screen must render — a Porkbun key scoped to no domain, or an account genuinely empty — and a domain list alone cannot express it. ⛔ total is the count before the page limit and is not decoration: a list that silently stops is the same shape as a complete one, and the customer's conclusion from it ("these are all my domains") is exactly the wrong one. Requires sites.view — seeing which domains you hold is not managing a credential.
पॅरामीटर्स
| नाव | प्रकार | आवश्यक | हे काय आहे |
|---|---|---|---|
provider (query) | ConnectionProvider | नाही | Show only one linked provider's domains, e.g. registrar_godaddy. |
state (query) | RegistrarDomainState | नाही | Show only domains in one state. |
प्रतिसाद
| नाव | प्रकार | आवश्यक | हे काय आहे |
|---|---|---|---|
items | RegistrarDomain[] | होय | — |
total | integer | होय | How many domains match before the page limit. ⛔ Compare it with items.length before telling a customer this is all of them. |
accounts | RegistrarAccount[] | होय | The linked accounts these domains came from — served here because an account with zero domains is a state the screen must render and a domain list cannot express. |
ही एंडपॉइंट परत करू शकेल अशा त्रुटी
401 · 403 · 422 · 429