Skip to main content
GET
/
api
/
webhooks
/
{id}
/
deliveries
/
{deliveryId}
Get Delivery
curl --request GET \
  --url https://app.opencomputer.dev/api/webhooks/{id}/deliveries/{deliveryId} \
  --header 'X-API-Key: <api-key>'
{
  "id": "msg_2aB…",
  "eventType": "sandbox.stopped",
  "eventId": "sb-3f9a…:sandbox.stopped",
  "payload": {
    "type": "sandbox.stopped",
    "sandboxId": "sb-3f9a…",
    "eventId": "sb-3f9a…:sandbox.stopped",
    "event": { "id": "sb-3f9a…:sandbox.stopped", "ts": "2026-06-24T12:00:00Z", "orgId": "org_…", "sandboxId": "sb-3f9a…", "type": "sandbox.stopped", "data": { "reason": "user_requested" } }
  },
  "timestamp": "2026-06-24T12:00:00Z"
}
Fetch one delivered message by id. See Webhooks.
The delivery provider’s attempt index and message store are eventually consistent: a message id can appear in list deliveries before this endpoint (and redeliver) can resolve it — observed up to ~30s+ after the attempt. So a 404 shortly after a delivery is transient — retry with backoff rather than treating it as final.
​
id
string
required
Destination ID (whk_…).
​
deliveryId
string
required
Message id (msg_…, the id from list deliveries; equals the svix-id header).
{
  "id": "msg_2aB…",
  "eventType": "sandbox.stopped",
  "eventId": "sb-3f9a…:sandbox.stopped",
  "payload": {
    "type": "sandbox.stopped",
    "sandboxId": "sb-3f9a…",
    "eventId": "sb-3f9a…:sandbox.stopped",
    "event": { "id": "sb-3f9a…:sandbox.stopped", "ts": "2026-06-24T12:00:00Z", "orgId": "org_…", "sandboxId": "sb-3f9a…", "type": "sandbox.stopped", "data": { "reason": "user_requested" } }
  },
  "timestamp": "2026-06-24T12:00:00Z"
}