syndication

GET /v1/syndication/runs/{runId}

One article's fan-out.

All syndication endpoints

Authentication

Send an API key as a bearer token. This endpoint does not state a specific permission in the specification, so give your key the least it needs and check the response rather than assuming.

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/syndication/runs/{runId} \
  -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 run and one post per channel, each with its own status, what it dropped and why, and what it cost. Gated on `syndication.view`.

Parameters

NameTypeRequiredWhat it is
runId (path)stringYes

Response

NameTypeRequiredWhat it is
idstringYes
placement_idstringYes
post_titlestringYes
article_urlstringYesThe article's REAL live URL, read back from the destination when it published. ⛔ Never a composed URL — the permalink structure belongs to the customer.
statusstring<pending, holding, complete>Yes⛔ `complete` means every channel SETTLED, not that every channel succeeded.
postsSyndicationPost[]Yes
created_atstringYes

Errors this endpoint can return

401 · 403 · 404