syndication

PUT `/v1/syndication/plans/{planId}`

Change a plan's channels or behaviour.

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 PUT https://api.zinndigital.com/v1/syndication/plans/{planId} \
  -H "Authorization: Bearer zdk_live_…" \
  -H "Content-Type: application/json" \
  -d '{ "scope": <string<post, recipe, org_default>> }'

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

Replaces the plan's channel set with `connection_ids`. ⛔ Each id is re-checked against the CALLER's scope, not merely the plan's org — a connection id is a UUID somebody could paste, and a plan naming another tenant's connection would post this article to that tenant's account. Gated on `syndication.manage`.

Parameters

Name	Type	Required	What it is
`planId (path)`	`string`	Yes	—

Request body

Name	Type	Required	What it is
`scope`	`string<post, recipe, org_default>`	Yes	—
`post_id`	`string`	No	—
`recipe_id`	`string`	No	—
`enabled`	`boolean`	No	—
`write_mode`	`string<ai_per_channel, one_text>`	No	—
`approval_mode`	`string<hold, send>`	No	—
`connection_ids`	`string[]`	No	—

Response

Name	Type	Required	What it is
`id`	`string`	Yes	—
`scope`	`string<post, recipe, org_default>`	Yes	Most specific wins — an article's own plan beats its recipe's beats the org default.
`post_id`	`string`	Yes	—
`recipe_id`	`string`	Yes	—
`enabled`	`boolean`	Yes	—
`write_mode`	`string<ai_per_channel, one_text>`	Yes	⚖️ Owner ruling 2026-08-20 — the AI writes per channel by default, because an X post and a LinkedIn update are not the same piece of writing.
`approval_mode`	`string<hold, send>`	Yes	⚖️ Owner ruling 2026-08-20 — hold for approval by default.
`channels`	`SyndicationPlanChannel[]`	Yes	—
`created_at`	`string`	Yes	—

Errors this endpoint can return

401 · 403 · 404

PUT /v1/syndication/plans/{planId}