For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
Fork this repoGet a demo
  • Docs
    • Welcome
    • Quickstart
    • Concepts
    • Search
    • MCP Server
    • CLI
    • Agent Skills
    • Connect
    • Add New Connector
    • Rate Limits
  • API Reference
      • GETList Messages
      • GETGet Message
      • GETList Subscriptions
      • GETGet Subscription
      • POSTCreate Subscription
      • PATCHUpdate Subscription
      • POSTRecover Failed Messages
      • DELDelete Subscription
LogoLogo
Fork this repoGet a demo
API ReferenceWebhooks

Recover Failed Messages

POST
/webhooks/subscriptions/:subscription_id/recover
POST
/webhooks/subscriptions/:subscription_id/recover
1import requests
2
3url = "https://api.airweave.ai/webhooks/subscriptions/550e8400-e29b-41d4-a716-446655440000/recover"
4
5payload = {
6    "since": "2024-03-14T00:00:00Z",
7    "summary": "Recover last 24 hours",
8    "value": {
9        "since": "2024-03-14T00:00:00Z",
10        "until": "2024-03-15T00:00:00Z"
11    }
12}
13headers = {
14    "x-api-key": "<apiKey>",
15    "Content-Type": "application/json"
16}
17
18response = requests.post(url, json=payload, headers=headers)
19
20print(response.json())
1{
2  "id": "rcvr_2bVxUn3RFnLYHa8z6ZKHMT9PqPX",
3  "status": "running"
4}
Retry failed message deliveries for a webhook subscription. Triggers a recovery process that replays all failed messages within the specified time window. This is useful when: - Your endpoint was temporarily down and you want to catch up - You've fixed a bug in your webhook handler - You want to reprocess events after re-enabling a disabled subscription Messages are retried in chronological order. Successfully delivered messages are skipped; only failed or pending messages are retried.
Was this page helpful?
Previous

Delete Subscription

Next
Built with

Retry failed message deliveries for a webhook subscription.

Triggers a recovery process that replays all failed messages within the specified time window. This is useful when:

  • Your endpoint was temporarily down and you want to catch up
  • You’ve fixed a bug in your webhook handler
  • You want to reprocess events after re-enabling a disabled subscription

Messages are retried in chronological order. Successfully delivered messages are skipped; only failed or pending messages are retried.

Authentication

x-api-keystring
API Key authentication via header

Path parameters

subscription_idstringRequired

The unique identifier of the subscription to recover messages for (UUID).

Request

This endpoint expects an object.
sincestringRequiredformat: "date-time"

Start of the recovery time window (inclusive). All failed messages from this time onward will be retried.

untilstring or nullOptionalformat: "date-time"

End of the recovery time window (exclusive). If not specified, recovers all failed messages up to now.

Response

Recovery task information
idstring

Unique identifier for this recovery task (Svix internal ID)

statusstring

Recovery task status: ‘running’ or ‘completed’

Errors

404
Not Found Error
422
Unprocessable Entity Error
429
Too Many Requests Error