support
GET /v1/sites/{siteId}/support-recommendations
What the support AI has advised about this site, and whether it was acted on.
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}/support-recommendations \
-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
Every recommendation raised about this site, newest first, in every state — including ones marked `ignored`. Showing the customer their own record is deliberate: it is what makes an automatic reply quoting earlier advice fair rather than an ambush. Requires `sites.view`.
Parameters
| Name | Type | Required | What it is |
|---|---|---|---|
siteId (path) | Uuid | Yes | The site whose advice history to read. |
Response
| Name | Type | Required | What it is |
|---|---|---|---|
items | SupportRecommendation[] | Yes | — |
live | integer | Yes | How many are still open — the number the panel badges. |
Errors this endpoint can return
401 · 403 · 404