Skip to main content
POST
List webhook delivery history

Restrictions

Authorizations

app_key
string
query
required

App key issued from the Flashduty console under Account → APP Keys. Required on every public API call. Keep it secret — it grants the same access as the owning account.

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

Page size.

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 integration ID.

Required range: x >= 0
event_types
string[]

Filter by event type values.

status
enum<string>

Filter by delivery status.

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
required

Paginated webhook delivery history.