List Partner Webhooks
This endpoint retrieves a complete list of all webhooks registered by a partner with the Netevia Banking platform. Each webhook object includes its configuration details such as event types, target URLs, and current status. Partners use this endpoint to audit, manage, and troubleshoot their webhook subscriptions that deliver real-time event notifications.
Endpoint
GET /api/Partners/webhooks
Authentication
Bearer token required. Obtain via:
POST https://api.banking.netevia.dev/api/auth/v2Include in header: Authorization: Bearer {token}
Token lifetime: 10 minutes. Refresh via POST /api/auth/refresh.
When to use
Use this endpoint when a partner needs a full overview of their registered webhook configurations, such as during an audit of active subscriptions or when troubleshooting missing event notifications. It is also useful before making updates or deletions to confirm which webhooks are currently registered and what their configurations are.
Response
200 OK
| Field | Type | Description |
|---|---|---|
| id | string | Unique identifier for the webhook registration |
| url | string | The target URL where event notifications are delivered |
| eventTypes | array | List of event types this webhook is subscribed to (e.g., transaction updates, account changes) |
| status | string | Current status of the webhook (e.g., active, inactive) |
| createdAt | string (ISO 8601) | Timestamp of when the webhook was registered |
| updatedAt | string (ISO 8601) | Timestamp of the most recent update to the webhook configuration |
[
{
"id": "wh_abc123def456",
"url": "https://partner.example.com/webhooks/netevia",
"eventTypes": [
"transaction.created",
"transaction.updated",
"account.status_changed"
],
"status": "active",
"createdAt": "2024-01-15T10:30:00Z",
"updatedAt": "2024-03-22T14:45:00Z"
},
{
"id": "wh_xyz789ghi012",
"url": "https://partner.example.com/webhooks/netevia-alerts",
"eventTypes": [
"card.issued",
"card.blocked"
],
"status": "inactive",
"createdAt": "2024-02-10T08:00:00Z",
"updatedAt": "2024-04-01T09:15:00Z"
}
]Error Codes
| Code | When it happens |
|---|---|
| 401 | Token missing, expired, or invalid |
| 403 | Insufficient permissions to access webhook configurations |
| 500 | Internal server error while retrieving the webhook list |
Common Mistakes
- Using an expired or missing Bearer token; tokens expire after 10 minutes and must be refreshed before making requests.
- Expecting a single object in the response — this endpoint returns a JSON array, even if only one webhook is registered.
- Forgetting to include the
Content-Type: application/jsonheader, which may cause the request to be rejected.
Related Endpoints
POST /api/Partners/webhooks— Register a new webhook for the partnerPUT /api/Partners/webhooks/{webhookId}— Update the configuration of an existing webhookDELETE /api/Partners/webhooks/{webhookId}— Remove a registered webhook
Example
curl -X GET https://api.banking.netevia.dev/api/Partners/webhooks \
-H "Authorization: Bearer YOUR_TOKEN" \
-H "Content-Type: application/json"Success