Authentication
Send an API key as a bearer token. The key must carry the links.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/content/posts/{postId} \
-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 post with its live placement counts. Gated on links.view. 404 rather than 403 for a post in another tenant — a 403 would confirm the row exists.
Parameters
| Name | Type | Required | What it is |
|---|---|---|---|
postId (path) | string | Yes | — |
Response
| Name | Type | Required | What it is |
|---|---|---|---|
id | string | Yes | — |
title | string | Yes | — |
body_html | string | Yes | The post body as HTML, exactly as the customer wrote it. The <a> tags in it are the anchors; the platform never rewrites them, on the way in or the way out. |
notes | string | Yes | The customer's own notes — V1's Post.notes. Never published. |
status | string<draft, ready> | Yes | — |
placement_count | integer | Yes | Sites this post is scheduled or live on. |
published_count | integer | Yes | — |
created_at | string | Yes | — |
updated_at | string | Yes | — |
Errors this endpoint can return
401 · 403 · 404