App events and webhooks listening for entry and asset (un)publish event topics will now receive extra headers when the action was triggered by a bulk action, scheduled action, or a release.

Prior to this change, an entry or asset (un)publish event did not provide context around what triggered the action, such as a collection of entries being published by a bulk action or a scheduled release.

Users can use these new headers to apply special logic, such as delaying a build if a bulk action or release triggered the app event or webhook.

Below is an example of some of the headers that may now be sent depending on the systems involved.

Bulk action headers

• x-contentful-bulk-action-id: The sys.id of the bulk action

Scheduled action headers

• x-contentful-scheduled-action-id: The sys.id of the scheduled action that triggered the action

Release headers

• x-contentful-release-id: The sys.id of the release that was actioned
• x-contentful-release-version-id: The sys.version of the release that was used for this action
• x-contentful-release-action-id: The sys.id of the release action used

Availability

These headers are now present on all app event subscriptions and webhooks impacted by one of the above APIs. No extra action is required to include these headers.

• Learn more about App Event subscriptions in our Extensibility Guide
• Learn more about Webhooks in our Content Management API documentation