links

GET /v1/content/target-presets

The headless CMS products we can publish to, and what each can carry.

Gbogbo àwọn links endpoints

Ìfàṣẹ́pọ̀

Fi bọ́kì kọ́kọ́ (bearer token) ránṣẹ́ gẹ́gẹ́ bí àmì ìdánimọ̀ API. Ibùdó yìí kò sọ àṣẹ pàtó kan nínú àlàyé rẹ̀, nítorí náà fún kọ́kọ́ rẹ̀ ní ohun tó kéré jù lọ tí ó nílò kí o sì ṣàyẹ̀wò ìdáhùn náà dípò kí o kàn rò ó.

Ojú abánisọ̀rọ̀ yìí kò gba id ajọ kankan. Kọ́kọ́rọ́ rẹ ti mọ ajọ ti o jẹ ti e, a o si fèsì nipa rẹ̀.

Gbiyanju rẹ

Rọ́pọ̀ èyíkéyìí nínú àwọn àmì ìtọ́ka < > pẹ̀lú iye tirẹ̀, àti àmì ìdánimọ̀ bọ́tìnnì náà pẹ̀lú bọ́tìnnì kan láti inú dásibọ̀ọ̀dù rẹ.

curl -X GET https://api.zinndigital.com/v1/content/target-presets \
  -H "Authorization: Bearer zdk_live_…"

Ṣé o ti wọlé? Iwọ̀n api ní nú ìgbékalẹ̀ rẹ kún id àjọ gidi rẹ ati bọtini tirẹ, o si nṣiṣẹ ibeere na lòdì si api gidi ki o le rii esi gidi na. Ṣí ojú abáná yìí sílẹ̀ nínú kọnsólù API

Àwọn kúlẹ̀kúlẹ̀

The catalogue the set-up screen offers — Payload, Strapi, Directus, Ghost, Shopify, Webflow and a custom endpoint — each with the capabilities that product actually supports and a hint telling the customer where to find their key. Gated on `links.view`. ⛔ The capability sets genuinely differ and are not decoration. Ghost is the only one with a first-class canonical-url field; Webflow claims almost nothing because a Webflow collection's fields are whatever the designer made them, and sending a field that does not exist is a validation error the customer cannot act on.

Idahun

OrúkọIruTí a nílòKini o jẹ
itemsCmsPreset[]Bẹẹni

Awọn aṣiṣe ti ibudo ipari yii le da pada

401 · 403