ai

GET /v1/ai/images/library

The images this organisation generated for its own use.

Dukkan ai wuraren ƙarshe

Tabbatar da Asali

Aika maɓallin API azaman alamar ɗauka (bearer token). Dole ne maɓallin ya kasance yana da izinin sites.view; idan babu shi, za a ƙi amfani da maɓallin tare da lambar 403, ba 404 ba.

Inda ID ɗin kungiyar ku ke zuwa

Wannan mahadar ta na daukar org_id a matsayin sigar tambaya. Bar shi kuma kiran zai shafi daukacin rukunin haya naka; aika shi don takaita kiran zuwa kungiya daya tak.

Ana samun lambar kungiyar ku a kan shafin maɓallan API a cikin madanninku, kusa da maɓallin kansa. Shi ne lambar da ta dace a kowane kiran da kuka yi.

Gwada

May gurbin komai da ke cikin kusurwa da ƙimar ka, kuma may gurbin maballi da maballi daga allon sarrafa ka.

curl -X GET https://api.zinndigital.com/v1/ai/images/library \
  -H "Authorization: Bearer zdk_live_…"

An shiga? Na'urar sarrafa API da ke cikin sashin kulawarka tana cika ainihin lambar ƙungiyarka da maɓallinka naka, sannan tana gudanar da buƙatar a kan ainihin API don haka zaka iya ganin amsar gaske. Buɗe wannan tashar a cikin na'urar kula da API

Bayani

The customer's own image library — every image they asked for directly, newest first, up to 200. Requires `sites.view`. ⛔ Filtered on `purpose = standalone`, not on an absent `post_id`. Those are not the same set: the featured-image backfill writes rows for a post that already lives on the customer's WordPress and identifies it by `site_id`/`remote_post_id` with `post_id` left null, so a null-based filter would put live site images into a personal library where deleting one destroys the record of a media upload. ⛔ No bytes and no URL on these rows, for the same reason the post rows carry none — the staged object is in a private bucket. Use the `file` endpoint.

Sigogi

SunaNau'iAna buƙataAbin da yake
org_id (query)UuidA'a

Martani

SunaNau'iAna buƙataAbin da yake
dataGeneratedImage[]Eh

Kuskuren da wannan matsaya za ta iya maido wa

401 · 403 · 429