Ferndesk

Changelog entry published

Fires when a changelog entry goes live: its first publish, or a publish after it was taken offline. Publishing edits to an entry that is already live does not fire it again, so it is safe to email your users from (check data.public first). Deduplicate on data.id if you only ever want one email per entry.

POST changelog_entry.published
Bearer token

Headers

· 3
webhook-id string required

Envelope id, unique per event.

webhook-timestamp string required

Unix seconds when the request was signed; reject stale values.

webhook-signature string required

Space-separated v1, tokens — several during secret rotation — computed as described under Signature verification.

Body

required application/json
id string required

Event identifier, repeated in the webhook-id header.

type string · enum required

Event type carried by this delivery.

values

  • changelog_entry.published
created_at string required

When the event was created.

data object required

The entry as it went live, with its body rendered as HTML and Markdown so you can send it on without another API call.

Responses