List dead-lettered deliveries to recover
const url = 'https://api.katara.com/katara/v1/orgs/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0/environments/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0/notification-recovery/deliveries?enrollment_id=2489E9AD-2EE2-8E00-8EC9-32D5F69181C0&enrollment_version=1';const options = {method: 'GET', headers: {Authorization: 'Bearer <token>'}};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request GET \ --url 'https://api.katara.com/katara/v1/orgs/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0/environments/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0/notification-recovery/deliveries?enrollment_id=2489E9AD-2EE2-8E00-8EC9-32D5F69181C0&enrollment_version=1' \ --header 'Authorization: Bearer <token>'Requires a signed-in human session and a current notification recovery operator enrollment of your own for this environment, as reviewing one delivery does; owner and administrator roles do not imply it. The enrollment is checked before anything is read. Each delivery is then checked as its review would be, and one whose recipient may no longer receive the event is left out, so a page can hold fewer entries than the limit while next_cursor is present. Addresses, provider receipts and the enrollment are not included.
Authorizations
Section titled “Authorizations”Parameters
Section titled “Parameters”Path Parameters
Section titled “Path Parameters”Query Parameters
Section titled “Query Parameters”Responses
Section titled “Responses”Dead-lettered deliveries in this environment, newest first.
object
A dead-lettered delivery and its event, as its review shows them.
object
object
object
Example
{ "data": [ { "event": { "producer": "account", "type": "account.security_changed", "schema_version": 1, "template_version": 1, "mode": "test", "resource_type": "account" }, "delivery": { "channel": "in_app", "state": "pending" } } ]}Headers
Section titled “Headers”default
Section titled “default”Refused or unavailable listing.
object
object
Stable; branch on it. Any operation can answer invalid_request, with param naming the refused field when there is one; human_session_required, when an API key, service account or workload calls an operation only a signed-in person may perform; reauthentication_required, when a person’s sign-in is too old for the operation; permission_denied; route_not_found and method_not_allowed, when no operation matches the path or method; and feature_unavailable, when the operation’s service is not enabled on this deployment.
The request field a refusal is about, such as the agent_id or run_id query parameter; null when the refusal is not about one field.
Example
{ "error": { "action": "sign_in" }}