Authentication
All requests require a workspace API key:$API_KEY for your API key. The key determines the workspace; you do not supply a workspace ID. See Authentication.
Path parameter
Query parameters
status=all, sort_by, and sort_order are not supported.
Request
Retrieve failed deliveries:Response
200 OK This fictional example has one failed Buyer among 20 Buyers in the complete Console. The filter restrictsdata; the counts still describe the whole Console.
Response fields
Console record
Eachdata item contains buyer and delivery:
buyerpreserves the same canonical public object returned by Retrieve a Buyer.deliverycontainsstatus,reason, andexecuted_atfor that Buyer at this Destination.
Delivery states
A successful delivery may have no reason:Counts and latest state
The Console returns one row per unique Buyer using its latest recorded delivery state. Multiple attempts or retries do not produce separate public rows for the same Buyer. Counts remain unchanged when applying astatus filter or moving between pages. If the selected filter has no matches, data is empty even when the overall counts are nonzero. If the entire Console is empty, all counts are zero.
Pagination
Keep the Destination ID and status filter unchanged when passing a cursor. The cursor is also bound to the workspace, endpoint, and fixed ordering.limit may change between pages. A mismatched or malformed cursor returns 400 invalid_cursor.
pagination.next_cursor is null. Delivery processing is continuous, so counts can change between requests.
Resource access
An inaccessible, missing, or deleted Destination returns 404. This endpoint does not retry deliveries, start workflows, or expose provider credentials and raw execution logs.Errors
Errors use the standard error envelope. Use
request_id when contacting support.