ai

GET /v1/ai/images/library

The images this organisation generated for its own use.

Dhammaan ai bixiyayaasha

Xaqiijinta aqoonsiga

U dir furaha API ah calaamad dusha ah (bearer token). Furaha waa inuu wataa ruqadda sites.view; furaha aan wadan waxaa loo diidayaa 403, ee ma aha 404.

Meesha aqoonsiga ururkaagu galayo

Endpoint-kani wuxතික org_id oo ah cabbir su'aal ah. Ka tag oo wicitaanku wuxuu daboolayaa dhammaan geedkaaga kiraynta; soo dir si aad wicitaanka ugu koobto hal urur.

Aqoonsiga ururkaagu wuxuu ku yaallaa shaashada furayaasha API ee dashboard-kaaga, oo ku xiga furaha laftiisa. Waa isku aqoonsi wicitaan kasta oo aad sameyso.

Isku day

Ku beddel wax kasta oo ku dhex jira qeebaha xaglaha ah qiimayaashaada, sidoo kalena haystaaha furaha ku beddel fure ka dhex muuqda dashboordigaaga.

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

Ma sign-garaysay? Qalabka API ee ku jira dashboard-kaagu wuxuu buuxiyaa aqoonsigaaga ururka ee dhabta ah iyo furahaaga gaarka ah, wuxuuna ku shaqeysiiyaa codsiga API-ga nool si aad u aragto jawaabta dhabta ah. Kani ka fur barta kontoroolka ee API

Faahfaahin

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.

Cabiraha

MagacaNoocLoo baahan yahayMaxay tahay
org_id (query)UuidMaya

Jawaab

MagacaNoocLoo baahan yahayMaxay tahay
dataGeneratedImage[]Haa

Cilladaha ay bartaani soo celin karto

401 · 403 · 429