GET /v1/sites/{siteId}/app/releases

Authentication

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

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 GET https://api.zinndigital.com/v1/sites/{siteId}/app/releases \
  -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

A Node.js, Python or Ruby site on our own servers deploys from Git as immutable releases: each deploy installs the commit into its own directory, installs its dependencies and runs the build there, and only then switches the live release. The last five are kept for instant rollback. Read from the server that runs the site, so a release pruned there is never offered. A release serving a branch preview carries preview_id and the branch it came from. Requires sites.view.

Parameters

Response

Errors this endpoint can return

401 · 403 · 404 · 422 · 429 · 503