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.
Body Params
object
-
webhookIdsarray of strings requiredThe webhook IDs whose notification history you want to search (max 25). Matching notifications across all listed webhooks are returned together. -
filtersobjectOptional filters to narrow resultsfilters object
-
startstringStart timestamp (default: now - 1 day). Supports ISO 8601 datetime (2023-01-01T00:00:00Z) or simple date (2023-01-01). -
endstringEnd timestamp (default: now). Supports ISO 8601 datetime (2023-12-31T23:59:59Z) or simple date (2023-12-31). -
enterpriseIdstringFilter by enterprise ID -
organizationIdstringFilter by organization ID -
walletIdstringFilter by wallet ID -
typestringFilter by notification type -
coinstringFilter by coin
-
-
offsetinteger int32 requiredNumber of records to skip (default 0) -
limitinteger int32 requiredNumber of records per page (default 50, max 50) -
retriggerboolean requiredIf 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.
Responses
200
Bulk webhook notification history retrieved successfully
Response Body
object
-
notificationsarray of objects requirednotifications object
-
idstring uuid required -
webhookIdstring required -
notificationRequestIdstring required -
urlstring required -
payloadstring required -
typestring required -
statusstring required -
retriesinteger int32 required -
createdAtstring date-time required -
updatedAtstring date-time required -
responsemap of objectsresponse object
-
<key>object
-
-
coinstring -
walletIdstring -
enterpriseIdstring -
organizationIdstring -
transferIdstring -
hashstring -
retriggeredNotificationRequestIdstring -
retriggerErrorstring
-
-
metadataobject requiredmetadata object
-
totalinteger int64 required -
limitinteger int32 required -
offsetinteger int32 required
-
400
Invalid request parameters
Response Body
object
-
namestring enum requiredError codeValidationFailedIllegalArgumentBadRequestDataIntegrityErrorNotImplementedErrorRETRIGGER_RATE_LIMITEDUSER_CREATION_FAILEDUSER_FALLBACK_FAILED -
errorstring requiredHuman-readable error message -
statusinteger enum int32 requiredHTTP status code400
403
Access denied for one or more webhook IDs
Response Body
object
-
namestring enum requiredError codeAccessDenied -
errorstring requiredHuman-readable error message -
statusinteger enum int32 requiredHTTP status code403
404
Webhook not found
Response Body
object
-
namestring enum requiredError codeNotFound -
errorstring requiredHuman-readable error message -
statusinteger enum int32 requiredHTTP status code404
500
Unexpected error occurred
Response Body
object
-
namestring enum requiredError codeUnexpectedErrorThirdPartyErrorDatabaseErrorUSER_FALLBACK_TIMEOUT -
errorstring requiredHuman-readable error message -
statusinteger enum int32 requiredHTTP status code500