GET /v1/cdn/targets

ማረጋገጫ

የAPI ቁልፉን እንደ bearer token ይላኩ። ቁልፉ የsites.create ፈቃድ ሊኖረው ይገባል፤ ይህ ፈቃድ የሌለው ቁልፍ በ404 ሳይሆን በ403 ውድቅ ይደረጋል።

ይህ ኤንድፖይ መክፈቻ (endpoint) የድርጅት መታወቂያ (organisation id) አይወስድም። የእርስዎ ቁልፍ (key) እሱ የሚመለከተውን ድርጅት አስቀድሞ ይለያል፣ እና ምላሹም ለዚሁ የተወሰነ ነው።

ሞክሩት

በቅንፍ ውስጥ ያለውን ማንኛውንም ነገር በራስዎ እሴቶች ይተኩ፣ እና ቁልፍ ቦታ ያዢውን ከዳሽቦርድዎ በመጣ ቁልፍ ይተኩ።

curl -X GET https://api.zinndigital.com/v1/cdn/targets \
  -H "Authorization: Bearer zdk_live_…"

ገብተዋል? የመቆጣጠሪያ ማዕከልዎ ውስጥ ያለው የኤፒአይ ኮንሶል ትክክለኛውን የድርጅት መታወቂያዎን እና የራስዎን ቁልፍ ይሞላል፣ እና ትክክለኛውን ምላሽ ማየት እንዲችሉ ጥያቄውን በቀጥታ ከሚሰራው ኤፒአይ ጋር ያካሂደዋል። ይህን ኤንድፖይንት በAPI ኮንሶል ውስጥ ይክፈቱ

ዝርዝሮች

The CDN destinations a site you are about to create could be placed on: Zinn®'s own pool, and one row per CDN account you have connected. ⛔⛤ This exists because the create wizard asked a boolean. "Use my own CDN" is a checkbox, and a checkbox cannot name one of two accounts — so a customer with two Cloudflare accounts said "mine" and the platform chose which. The wizard also showed that checkbox only when a connected provider was literally cloudflare, so an account on Bunny or CDN77 had no control at all and no explanation for its absence. ⛔ Pass product_line. It is the one input that changes the answer: on a platform-managed line (Footprint-Free) creating straight onto your own account is refused — every site on one account can be linked to every other on it, which is what that line is sold to prevent — so each account comes back listed, unavailable, with reason: line_is_platform_managed. Listing it and saying why is the point: a customer who cannot find their account concludes the connection failed. ⭐ changes_nameservers is the field to render before the customer commits. A zone-owning CDN assigns nameservers per account, so choosing your own account means your registrar must be pointed at that account's pair. Advisory and read-only; the create itself re-checks everything. Requires sites.create.

መለኪያዎች

ምላሽ

ይህ ማብቂያ ሊመልሳቸው የሚችሉ ስህተቶች

401 · 403 · 429