Get started
Webhooks

Recover missed events

Recover missed events

When your endpoint was down longer than the retries, three calls bring it back in step.

You want toCall
Deliver one event againPOST …/webhook-deliveries with event_id, up to 30 days back
Deliver every event since a momentPOST …/webhook-deliveries with since, up to 30 days back
Find what you missedGET …/webhook-events, up to 13 months back

The samples use the management key and an owner's or admin's session token, as in Webhook endpoints.

Resend one event

Pass the event's id and the endpoint to send it to.

curl -s -X POST "https://api.mountaya.com/v1/organizations/$MOUNTAYA_ORGANIZATION_ID/webhook-deliveries" \
  -H "X-API-Key: $MOUNTAYA_MANAGEMENT_KEY" \
  -H "X-Session-Token: $MOUNTAYA_SESSION_TOKEN" \
  -H "Idempotency-Key: $(uuidgen)" \
  -H "Content-Type: application/json" \
  -d "{\"webhook_endpoint_id\": \"$MOUNTAYA_WEBHOOK_ENDPOINT_ID\", \"event_id\": \"019a8eed-e1ad-7753-b049-b0e20d79577a\"}" \
  | jq '.data | {id, kind, delivery_id}'
Response
{
  "id": "019a8ef1-3b6d-7c20-9a4e-1f8d2c7b5e93",
  "kind": "resend",
  "delivery_id": "019a8ef1-3b70-7d41-8c2e-5a9f0b1d4e67"
}

The event arrives with its original id, so your deduplication still holds.

Redeliver since a moment

Pass since to send again every event the endpoint subscribes to, recorded from that moment on. Mountaya sends them oldest first, at the pace your endpoint takes them.

curl -s -X POST "https://api.mountaya.com/v1/organizations/$MOUNTAYA_ORGANIZATION_ID/webhook-deliveries" \
  -H "X-API-Key: $MOUNTAYA_MANAGEMENT_KEY" \
  -H "X-Session-Token: $MOUNTAYA_SESSION_TOKEN" \
  -H "Idempotency-Key: $(uuidgen)" \
  -H "Content-Type: application/json" \
  -d "{\"webhook_endpoint_id\": \"$MOUNTAYA_WEBHOOK_ENDPOINT_ID\", \"since\": \"2026-11-14T06:00:00Z\"}" \
  | jq '.data | {id, kind, since}'

Redeliver after an outage, or after you enable an endpoint again. A disabled endpoint must be enabled first.

Reconcile with the event list

GET …/webhook-events lists every event recorded in your organization for 13 months, sent or not. Start from the last event you processed, and skip the ids you have already seen.

curl -s "https://api.mountaya.com/v1/organizations/$MOUNTAYA_ORGANIZATION_ID/webhook-events?start_at=2026-11-14T06:00:00Z&limit=100" \
  -H "X-API-Key: $MOUNTAYA_MANAGEMENT_KEY" \
  -H "X-Session-Token: $MOUNTAYA_SESSION_TOKEN" \
  | jq '{events: [.data[] | {id, type, created_at}], next_cursor: .extensions.metadata.pagination.next_cursor}'
Response
{
  "events": [
    {
      "id": "019a8eed-e1ad-7753-b049-b0e20d79577a",
      "type": "organization.member.updated",
      "created_at": "2026-11-14T09:12:44Z"
    }
  ],
  "next_cursor": null
}

Each event is the envelope a delivery carries, so one handler serves both.

Next steps

Last updated