GET /v1/sites/{site_id}/translation/served

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/{site_id}/translation/served \
  -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

The served_locales the customer chose on the site's Translation tab. The Zinn® Translate plugin publishes exactly this list when it is connected to a Zinn Digital® plan — it asks when it connects and then hourly, keeps the answer, and never asks during a page load. A separate read from getSiteTranslation on purpose: that payload counts every translation the site has to report per-language progress, and this one is asked hourly by every connected site, so it answers from one row. ⛔ An empty list means publish none — never "all". A site with no Site Translation answers 200 with state: disabled and an empty list rather than a 403, so the plugin can tell "publish nothing" apart from "could not ask"; nothing paid for is returned here. Requires sites.view, the same scope as the bundle.

Parameters

Response

Errors this endpoint can return

401 · 403 · 404