DELETE `/v1/ai/images/library/{imageId}`

Throw one of your own generated images away.

Authentication

Send an API key as a bearer token. The key must carry the links.edit permission; a key without it is refused with 403, not 404.

Where your organisation id goes

This endpoint takes org_id as a query parameter. Leave it out and the call covers your whole tenancy subtree; send it to narrow the call to one organisation.

Your organisation id is on the API keys screen in your dashboard, beside the key itself. It is the same id in every call you make.

Try it

Replace anything in angle brackets with your own values, and the key placeholder with a key from your dashboard.

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

Signed in? The API console in your dashboard fills in your real organisation id and your own key, and runs the request against the live API so you can see the actual response. Open this endpoint in the API console

Details

Deletes the row **and the stored object**. Requires `links.edit`. ⛔ Only a `standalone` row. A post image's row records the media id its upload was given, and losing that turns a re-publish into a duplicate in the customer's media library. ⛔ Storage failure is not fatal: the customer's row goes either way, and the 90-day lifecycle rule reclaims the bytes.

Parameters

Name	Type	Required	What it is
`imageId (path)`	`Uuid`	Yes	—
`org_id (query)`	`Uuid`	No	—

Errors this endpoint can return

401 · 403 · 404 · 429