Skip to main content
A webhook acknowledgement tells theStacc whether the receiver accepted the request. It does not prove that the public article has rendered. Return a supported status and, when available, a JSON object with the actual stored CMS ID and public article URL. Do not acknowledge a change your receiver deliberately ignored.

Accepted statuses and response fields

The Custom Webhook paths differ. Use id and url as the common response field names for publication, rather than depending on aliases that only one path reads.

Custom Webhook acknowledgement handling by delivery path

Delivery pathHTTP statuses accepted before body checksResponse fields read
Manual publish or republish200, 201, 202, 204URL: url or published_url. CMS ID: id.
Scheduled publishAny 2xx, subject to response-body rejection checksURL: url, post_url or permalink. CMS ID: id, post_id or external_id.
Sync200, 201, 202, 204Checks for an explicit rejection. Does not use response url or id to refresh the stored article identity or live link.
This illustrative successful publication response uses the shared field names:
Return values from the article actually stored by your receiver. Keep a blog_id-to-CMS-record mapping for later updates. The publication and Sync payloads described in the field reference do not include a separate external_post_id field, so do not assume a returned ID will appear in every subsequent update request.

Explicit rejection in a successful HTTP response

An accepted status can still carry a failure. The response parser recognizes these explicit boolean flags: ignored: true, applied: false, handled: false, processed: false, ok: false and success: false. A flag must be a JSON boolean; a count or a string is not the same indication. For example, this illustrative response reports an unhandled event even if the HTTP status is 200:
The scheduled publisher classifies an explicit rejection by its reason. Temporary conditions can remain eligible for a bounded retry; unsupported or permanent refusals stop that path. An explicit validation rejection can also make a server-error response permanent. Manual publishing and Sync surface the rejection without entering that scheduled backoff solely because the response says to retry. See idempotency and retries for the delivery policy. Describe a failure accurately and do not return ok: true for an event you skipped without applying it. If your receiver accepts work into a durable queue, define what is acknowledged and how the later result is checked. An acknowledgement is not a substitute for completing or tracking the job.

Missing JSON, IDs or public URLs

An empty or non-JSON body can acknowledge a supported publication request, but it supplies no JSON ID or URL fields to extract. Prefer a JSON object when you want those fields recorded. A non-object JSON value also does not supply the expected named fields. This does not waive the status and explicit-rejection checks above. A public-URL template can provide a dashboard link when the publication response has no usable URL. The current resolver can also replace a section-root URL with a templated or slug-appended article URL. These are link-construction rules, not requests that verify the public page. Return the correct absolute article URL instead of a generic blog index, and check the resulting link on your website. Handle test.ping and preview-prefixed sample blog IDs as tests rather than inserting production articles. A successful test does not establish that your receiver handles a real blog.updated event, maps its fields correctly or completes downstream publication. Confirm those behaviours with your own receiver fixtures before enabling writes.