Retrieve a paginated history of webhook notifications sent to a partner within a specified date range.
Partner's Webhooks Log
This endpoint retrieves the logs of webhook notifications sent to a partner within a specified time range. It allows partners to monitor webhook delivery, inspect past payloads, and troubleshoot potential issues with event delivery or endpoint availability.
Endpoint
GET /api/Partners/webhooks/log
Authentication
Bearer token required. Obtain via:
POST https://api.banking.netevia.dev/api/auth/v2
Include in header: Authorization: Bearer {token}
Token lifetime: 10 minutes. Refresh via POST /api/auth/refresh.
When to use
Use this endpoint when you need operational visibility into webhook activity between Netevia and your platform. It is especially useful for debugging failed webhook deliveries, auditing the event flow for a specific time window, or confirming that webhook notifications were successfully received by your endpoint.
Query Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
startDate | string (date-time) | No | Start of the date range for filtering logs. ISO 8601 format (e.g., 2025-04-01T00:00:00Z). |
endDate | string (date-time) | No | End of the date range for filtering logs. ISO 8601 format (e.g., 2025-04-10T23:59:59Z). |
skip | integer (int32) | No | Number of records to skip for pagination. Defaults to 0. |
take | integer (int32) | No | Number of records to return per page. Defaults to 100. |
Response
200 OK
Returns a list of webhook log entries for the partner within the requested date range. Each entry typically includes delivery status, timestamps, event type, and response data from your endpoint.
[
{
"id": "whl_a1b2c3d4e5f6",
"eventType": "transaction.completed",
"webhookUrl": "https://your-platform.com/webhooks/netevia",
"statusCode": 200,
"requestPayload": "{\"eventType\":\"transaction.completed\",\"transactionId\":\"txn_001\"}",
"responseBody": "{\"received\":true}",
"attemptedAt": "2025-04-05T14:22:10Z",
"deliveredAt": "2025-04-05T14:22:11Z",
"success": true
},
{
"id": "whl_b2c3d4e5f6a7",
"eventType": "account.created",
"webhookUrl": "https://your-platform.com/webhooks/netevia",
"statusCode": 503,
"requestPayload": "{\"eventType\":\"account.created\",\"accountId\":\"acc_002\"}",
"responseBody": "Service Unavailable",
"attemptedAt": "2025-04-06T09:10:05Z",
"deliveredAt": null,
"success": false
}
]Error Codes
| Code | When it happens |
|---|---|
| 400 | Invalid query parameter values or malformed date-time format |
| 401 | Token missing, expired, or invalid |
| 403 | Insufficient permissions to access partner webhook logs |
| 404 | No webhook log resource found for the partner |
| 500 | Internal server error while retrieving logs |
Common Mistakes
- Providing
startDateorendDatein a non-ISO 8601 format will result in a 400 error; always use the formatYYYY-MM-DDTHH:MM:SSZ. - Omitting both
startDateandendDatemay return all available logs or a default recent range — use explicit dates for predictable results. - Setting
taketo a very large value without combining it withskipmay result in slow responses; use pagination to navigate large result sets efficiently. - The
skipparameter is zero-based; to retrieve the second page of 50 records, setskip=50&take=50.
Related Endpoints
GET /api/Partners/webhooks— Retrieve configured webhook endpoints for the partnerPOST /api/Partners/webhooks— Register a new webhook endpoint for the partnerDELETE /api/Partners/webhooks/{webhookId}— Remove a registered webhook endpoint
Example
curl -X GET "https://api.banking.netevia.dev/api/Partners/webhooks/log?startDate=2025-04-01T00:00:00Z&endDate=2025-04-10T23:59:59Z&skip=0&take=50" \
-H "Authorization: Bearer YOUR_TOKEN" \
-H "Content-Type: application/json" 200Success
