Skip to main content
POST
List webhook delivery history

Restrictions

Usage

  • start_time and end_time are Unix milliseconds.
  • Each record is one delivery of one event to one endpoint; attempt counts the HTTP tries, which are retried only on connection errors.
  • Stored request and response headers and bodies are truncated.
  • Pass search_after_ctx from the previous response for the next page; it is an empty string on the last page.
  • Returns InvalidParameter when delivery history recording is turned off for the deployment.

Authorizations

app_key
string
query
required

APP Key created in the Flashduty console under My → APP Key. Send it as the app_key query parameter or in the Fd-App-Key request header. Its effective access is the intersection of the key's permission scope and the creator's current role permissions. Keep it secret.

Body

application/json

Filter parameters for listing outbound webhook delivery history. The query is bounded by a required millisecond time window; use search_after_ctx for cursor-based pagination.

limit
integer
required

Number of records per page, 1–100.

Required range: 1 <= x <= 100
start_time
integer<int64>
required

Window start time in Unix milliseconds.

Required range: 1000000000000 <= x <= 9999999999999
end_time
integer<int64>
required

Window end time in Unix milliseconds. Must be greater than start_time.

Required range: 1000000000000 <= x <= 9999999999999
search_after_ctx
string

Opaque cursor returned by a previous call for fetching the next page.

asc
boolean

Ascending order by event_time when true; otherwise descending.

orderby
enum<string>

Sort field. Currently only event_time is supported.

Available options:
event_time
ref_id
string

Reference ID filter (incident or alert ID).

Maximum string length: 128
integration_id
integer<int64>

Filter by webhook integration ID; 0 or omitted returns all integrations.

Required range: x >= 0
event_types
string[]

Filter by event type codes (e.g. i_new incident created, a_new alert triggered).

status
enum<string>

Filter by delivery status: success or failed.

Available options:
success,
failed

Response

Success

Success response envelope. On every 2xx response, request_id identifies the call (also mirrored in the Flashcat-Request-Id header) and data holds the endpoint-specific payload. Failure responses use a different shape — see ErrorResponse.

request_id
string
required

Unique ID for this request. Mirrored in the Flashcat-Request-Id response header. Include it when reporting issues.

Example:

"01HK8XQE3Z7JM2NTFQ5YJ8P9R4"

data
object

Paginated webhook delivery history.