Partner's Webhooks Log

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

ParameterTypeRequiredDescription
startDatestring (date-time)NoStart of the date range for filtering logs. ISO 8601 format (e.g., 2025-04-01T00:00:00Z).
endDatestring (date-time)NoEnd of the date range for filtering logs. ISO 8601 format (e.g., 2025-04-10T23:59:59Z).
skipinteger (int32)NoNumber of records to skip for pagination. Defaults to 0.
takeinteger (int32)NoNumber 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

CodeWhen it happens
400Invalid query parameter values or malformed date-time format
401Token missing, expired, or invalid
403Insufficient permissions to access partner webhook logs
404No webhook log resource found for the partner
500Internal server error while retrieving logs

Common Mistakes

  • Providing startDate or endDate in a non-ISO 8601 format will result in a 400 error; always use the format YYYY-MM-DDTHH:MM:SSZ.
  • Omitting both startDate and endDate may return all available logs or a default recent range — use explicit dates for predictable results.
  • Setting take to a very large value without combining it with skip may result in slow responses; use pagination to navigate large result sets efficiently.
  • The skip parameter is zero-based; to retrieve the second page of 50 records, set skip=50&take=50.

Related Endpoints

  • GET /api/Partners/webhooks — Retrieve configured webhook endpoints for the partner
  • POST /api/Partners/webhooks — Register a new webhook endpoint for the partner
  • DELETE /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"
Query Params
date-time
date-time
int32
Defaults to 0
int32
Defaults to 100
Response
200

Success

Language
Credentials
Bearer
JWT
LoadingLoading…
Response
Click Try It! to start a request and see the response here!