POST /v1/media-offload/uploads

Authentication

This endpoint does not take an API key. It takes its own credential, issued to the plugin or service that calls it, as a bearer token; see the description above.

This endpoint takes no organisation id. Your key already identifies the organisation it belongs to, and the response is scoped to it.

Try it

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

curl -X POST https://api.zinndigital.com/v1/media-offload/uploads \
  -H "Authorization: Bearer zdk_live_…" \
  -H "Content-Type: application/json" \
  -d '{ "keys": <string[]> }'

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

Called by the Zinn® Media Offload plugin with a bearer plugin token. Returns one presigned PUT URL per key; the plugin then sends the bytes straight to storage, so no file ever transits this API and no storage credential ever reaches WordPress. Up to 100 keys per request. Presigning is local cryptography with no vendor round trip, so a batch costs no more than a single key — which is what makes offloading an existing 20,000-file media library 200 requests rather than 20,000. Every key is joined onto the site's own prefix and validated. A key that tries to climb out of that prefix is refused with 422, never normalised into something plausible. An offload writing to our storage answers 422 with code: FEATURE_NOT_INCLUDED and no URLs once the organisation no longer holds a plan that includes object storage — checked on every request, because a plugin token outlives the plan that paid for it (D26223). An offload writing to the customer's own bucket is unaffected.

Request body

Response

Errors this endpoint can return

401 · 422 · 429 · 503