Sign in
latestOpenAPI 3.0.32026-08-224982,0272.8 MB

e445c15e5bee

Notification Webhooks

Get or retrigger webhook notifications across multiple webhooks

Searches notification history across up to 25 webhooks and, optionally, resends the matches. Use this endpoint when you do not have specific notification IDs on hand and instead want to find (and optionally resend) notifications by criteria such as a time range, wallet, notification type, or coin. A common case is recovering from a downtime window on your endpoint: supply the webhook ID and a start/end time, set 'retrigger' to true, and every matching notification from that window is resent. If you already know the exact notification ID(s) you want to resend, use the single-webhook retrigger endpoint (POST /webhooks/{webhookId}/notifications/retrigger) instead.

post/api/notifications/v1/webhooks/notifications

Request body

webhookIdsstring[] required

The webhook IDs whose notification history you want to search (max 25). Matching notifications across all listed webhooks are returned together.

offsetinteger required

Number of records to skip (default 0)

limitinteger required

Number of records per page (default 50, max 50)

retriggerboolean required

If true, every notification matched by this request is resent after being fetched. Set this when you want to resend all notifications matching your filters (for example, everything within a time window) without needing their individual notification IDs. The retrigger outcome (success or error) is returned inline on each notification. Subject to per-webhook rate limits (default 50/min). Default: false.

Example request

{
  "filters": {
    "start": "2023-01-01T00:00:00.000Z",
    "end": "2023-12-31T23:59:59.000Z",
    "enterpriseId": "ent-abc123",
    "organizationId": "org-xyz789",
    "walletId": "wallet-def456",
    "type": "transfer",
    "coin": "btc"
  },
  "limit": 50
}

Response

Bulk webhook notification history retrieved successfully