Skip to main content
POST
/
ops
/
dead-letter
/
{event_id}
/
retry
Retry Dead Letter Event
curl --request POST \
  --url https://api.example.com/ops/dead-letter/{event_id}/retry
{
  "event_id": "<string>",
  "provider": "<string>",
  "resource_type": "<string>",
  "resource_name": "<string>",
  "event_type": "CREATE",
  "payload": {},
  "correlation_id": "<string>",
  "created_at": "2023-11-07T05:31:56Z",
  "previous_config": {},
  "status": "pending",
  "published_at": "2023-11-07T05:31:56Z"
}

Path Parameters

​
event_id
string
required

Response

Successful Response

Event response.

Attributes: event_id: Unique identifier for this event. provider: Provider name (e.g., "postgres"). resource_type: Resource type (e.g., "database"). resource_name: Resource name from manifest. event_type: Type of lifecycle event (CREATE, UPDATE, DELETE). payload: Resource configuration as JSON object. previous_config: Previous configuration for UPDATE events. correlation_id: Correlation ID for tracing. status: Processing status (pending, published). created_at: When event was created. published_at: When event was processed.

​
event_id
string
required
​
provider
string
required
​
resource_type
string
required
​
resource_name
string
required
​
event_type
enum<string>
required

Resource lifecycle event type: CREATE, UPDATE, or DELETE.

Available options:
CREATE,
UPDATE,
DELETE
​
payload
Payload · object
required
​
correlation_id
string
required
​
created_at
string<date-time>
required
​
previous_config
Previous Config · object
​
status
enum<string>
default:pending

Status of an event.

Attributes: PENDING: Event created but not yet processed. PUBLISHED: Event successfully processed.

Available options:
pending,
published
​
published_at
string<date-time> | null