links
POST /v1/content/runs
Start a multi-site posting run.
Аутентификација
Пошаљите API кључ као bearer токен. Ова крајња тачка не наводи конкретну дозволу у спецификацији, па свом кључу доделите најмања неопходна овлашћења и проверите одговор уместо да претпостављате.
Ова крајња тачка не прихвата id организације. Ваш кључ већ идентификује организацију којој припада, а одговор је ограничен на њу.
Испробајте
Замените све што је у угластим заградама сопственим вредностима, а чувар места кључа кључем са своје контролне табле.
curl -X POST https://api.zinndigital.com/v1/content/runs \
-H "Authorization: Bearer zdk_live_…" \
-H "Content-Type: application/json" \
-d '{ "brief": <string>, "site_ids": <string[]> }'Пријављени сте? API конзола на вашој контролној табли попуњава ваш прави id организације и ваш сопствени кључ, и покреће захтев према живом API-ју како бисте могли да видите стварни одговор. Отворите ову крајњу тачку у API конзоли
Детаљи
Writes one article from the brief and places it on every site named, eight at a time. Answers 201 immediately with the run row — the work itself happens on the durable queue, and the run screen shows it progressing. Gated on links.edit, the same key as scheduling a post by hand, because that is what this creates. ⛔ publish_policy defaults to draft_only, so a request that omits it produces scheduled drafts and puts nothing live. unattended is the only value that publishes without a human, and it is the mode the durability guarantees are written for. ⛔ Every site id must belong to this organisation. A run naming a site that does not is refused whole with 422 rather than quietly posting to the rest — "it only posted to some of them" is not a state a customer can act on. Sites that cannot receive a post (suspended, a non-WordPress stack, transferred away) are recorded as skipped with a reason and do not stop the run.
Тело захтева
| Назив | Тип | Обавезно | Шта је ово |
|---|---|---|---|
brief | string | Да | — |
site_ids | string[] | Да | — |
anchors | ContentRunAnchor[] | Не | — |
category | string | Не | — |
publish_policy | ContentRunPublishPolicy | Не | — |
recipe_id | string | Не | — |
Одговор
| Назив | Тип | Обавезно | Шта је ово |
|---|---|---|---|
id | string | Да | — |
state | ContentRunState | Да | Where a run got to. partial is a real, honest, terminal answer and not a euphemism: some sites published and some did not, nothing is left to try, and the failures can be… |
publish_policy | ContentRunPublishPolicy | Да | How far a run may go on its own. draft_only is the default and puts nothing live. |
recipe_id | string | Не | — |
brief | string | Да | — |
category | string | Не | — |
post_id | string | Не | The article this run wrote. Written once and reused for every site, so a resumed run places the SAME copy rather than paying for a second generation. |
attempt | integer | Да | Which pass over the failures this is. 0 is the original run. |
workflow_id | string | Не | — |
totals | ContentRunTotals | Да | — |
reason | ContentRunFailureReason | Не | — |
provider | string | Не | — |
message | string | Не | An English sentence for the customer. Clients should render their own localised text from reason and fall back to this only for a code they do not know. |
resumable | boolean | Да | Whether a resume would actually do anything. False on a paused run with nothing failed — do not offer the button when this is false. |
started_at | string | Не | — |
finished_at | string | Не | — |
created_at | string | Да | — |
items | ContentRunItem[] | Да | — |
Грешке које ова крајња тачка може вратити
401 · 403 · 422 · 503