Skip to main content

Get webhook events

Retrieve recent webhook events for the authenticated account.

See which events were processed successfully and when, which are queued or waiting for an automatic retry, and which need investigation. Use this history to review webhook activity from the past 30 days. Each entry represents one event for one subscription. For the current subscriptions themselves, see Get webhook subscriptions.

Request​

Endpoint​

GET https://api.woodpecker.co/rest/v2/webhooks/events

Headers​

x-api-key: {YOUR_API_KEY}

For details on how to authenticate your requests, please see the authentication guide.

Parameters​

ParameterRequiredTypeDescription
event_typeNostringLowercase event name, such as prospect_replied. Use a name from available events
created_fromNostringEarliest event creation time to include, e.g. 2026-10-28T00:00:00+01:00
created_toNostringLatest event creation time to include, e.g. 2026-10-29T00:00:00+01:00
next_page_cursorNostringCursor returned by the previous page. See pagination

On the first page, you can combine the filters or omit them all. Send each filter at most once.

Both date filters require a numeric time zone offset (e.g., +00:00 for UTC). When constructing URLs manually, encode the + sign as %2B. Both bounds are inclusive.

Request samples​

Get reply events created on or after October 28, 2026​

curl --request GET \
--url "https://api.woodpecker.co/rest/v2/webhooks/events?event_type=prospect_replied&created_from=2026-10-28T00%3A00%3A00%2B01%3A00" \
--header "x-api-key: {YOUR_API_KEY}"

Response​

Response examples​

If no events match, events is an empty array and next_page_cursor is null.

{
"events": [
{
"id": 12346,
"webhook_config_id": 98765,
"name": "Replies",
"event_type": "prospect_replied",
"target_url": "https://hooks.example.com/replies",
"created_at": "2026-10-28T12:10:00+01:00",
"processing_started_at": "2026-10-28T12:10:04+01:00",
"processing_finished_at": "2026-10-28T12:10:05+01:00",
"auto_retry_after": null,
"status": "processed",
"reason": null
},
{
"id": 12345,
"webhook_config_id": 98764,
"name": "CRM replies",
"event_type": "prospect_replied",
"target_url": "https://crm.example.com/webhooks/replies",
"created_at": "2026-10-28T12:00:00+01:00",
"processing_started_at": null,
"processing_finished_at": null,
"auto_retry_after": "2026-10-28T12:11:05+01:00",
"status": "waiting_for_retry",
"reason": "processing_error"
}
],
"next_page_cursor": "ZXhhbXBsZS1wYWdlLWN1cnNvcg"
}

Body schema​

Timestamps use ISO 8601 with a time zone offset.

FieldTypeDescription
events[]arrayWebhook event history entries
  └─ idintegerUnique event ID. Use it to retry a webhook event
  └─ webhook_config_idintegerID shared by events for the same subscription. Use it to resume a webhook subscription
  └─ namestring or nullCurrent webhook subscription name
  └─ event_typestringEvent name. See available events
  └─ target_urlstringCurrent URL configured for the webhook
  └─ created_atstringWhen the event entered the webhook queue
  └─ processing_started_atstring or nullWhen the event was picked up for processing
  └─ processing_finished_atstring or nullWhen the event finished processing
  └─ auto_retry_afterstring or nullEarliest time Woodpecker can retry the delivery of the webhook. Populated for the waiting_for_retry status
  └─ statusstringProcessing status
  └─ reasonstring or nullReason for the processing status.
  • data_changed - The data needed to build the payload changed after the event was recorded
  • resource_not_found - A record needed to build the payload could not be found
  • processing_error - An error occurred during processing or delivery
  • unknown - More specific reason is unavailable
  • null - No reason applies
next_page_cursorstring or nullCursor to use for the next page. See pagination

Event statuses​

Use status and reason together to decide what to do.

StatusWhat it meansWhat to do
pendingThe event is queued for processingWait and check again
waiting_for_retryThe event is waiting for the next automatic delivery attemptCheck that your server is reachable and returns a 2xx response. Wait until auto_retry_after or resume the subscription to lift the delay for all its queued events
processingThe event is being processedWait and check again
processedThe event was processed successfullyCheck the receiving application's logs to confirm receipt. If your integration needs another delivery, retry the event
skippedThe event was skipped because the data needed to build the payload changed or is no longer availableCheck reason and verify that the related prospect, campaign, or other record still exists and has the expected data
failedThe event could not be processedCheck reason and address the cause before you retry the event. If the cause is unclear, contact support with the event id and reason
unknownThe event's processing status could not be determinedCheck again. If the status persists and the event is missing from your integration, contact support with the event id

See the webhooks guide for how Woodpecker handles delivery errors.

Pagination​

Each page contains up to 100 events, newest first.

  • For the first page, omit next_page_cursor and send any filters you want to apply.
  • For the next page, send the returned next_page_cursor. The cursor retains the original filters. Any filters you send with it are ignored.
  • When the response returns next_page_cursor as null, you have reached the last page.
curl --request GET \
--url "https://api.woodpecker.co/rest/v2/webhooks/events?next_page_cursor={NEXT_PAGE_CURSOR}" \
--header "x-api-key: {YOUR_API_KEY}"