Accepted statuses and response fields
The Custom Webhook paths differ. Useid 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 path | HTTP statuses accepted before body checks | Response fields read |
|---|---|---|
| Manual publish or republish | 200, 201, 202, 204 | URL: url or published_url. CMS ID: id. |
| Scheduled publish | Any 2xx, subject to response-body rejection checks | URL: url, post_url or permalink. CMS ID: id, post_id or external_id. |
| Sync | 200, 201, 202, 204 | Checks for an explicit rejection. Does not use response url or id to refresh the stored article identity or live link. |
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:
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. Handletest.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.