Webhooks overview
Use the Webhooks API to inspect event history and delivery attempts, retrieve individual events, and resend supported events.
Review delivery history or browse the operations in this category.
Learn how to receive and process Gravv events reliably.
How it works
Gravv delivers webhook events to your configured endpoint as things happen — account changes, inflows, transfers, card activity, collections, and KYC decisions. These API endpoints give you observability and control over that delivery pipeline:
- Audit what was sent with the event history, filterable by event type, status, and date range.
- Debug failures by inspecting an individual event — including request/response headers and payload — and its per-attempt call history.
- Recover by manually retrying a failed event.
For the list of event types and payload shapes, see the webhooks integration guide.
Endpoints
| Endpoint | Description |
|---|---|
GET /v1/webhooks/history |
Paginated webhook event history with event-type, status, and date filters |
GET /v1/webhooks/event/{id} |
Event details including headers, payload, and delivery attempts |
GET /v1/webhooks/calls/{id} |
Per-attempt delivery call history for an event |
POST /v1/webhooks/event/send/{id} |
Trigger an immediate manual redelivery (requires the webhook:create permission) |
Authentication
All requests use https://api.gravv.xyz/v1/ and authenticate with the Api-Key header. See Authentication for details.
Was this page helpful?