Update webhook (V2)
Webhooks
Update webhook
Updates the URL, active state, and linked alerts of a webhook.
PUT
Update webhook (V2)
Overview
Updates a webhook. The request body replaces the entire webhook configuration — include all fields you want to keep, not just the ones you are changing.Rate limit: 20 requests per 60 seconds per token.
Endpoint
PUT /api/v2/webhooks/{id}
Path parameters
Webhook ID.
Request body
| Field | Type | Required | Description |
|---|---|---|---|
| url | string | Yes | Destination URL |
| alertIds | integer[] | Yes (unless isGlobal) | Alert configuration IDs to link |
| isActive | boolean | No | Enable or disable deliveries |
| isGlobal | boolean | No | Enable global delivery |
Response
200 OK —WebhookDto with updated values.
Error responses
| Status | Meaning |
|---|---|
| 401 | Missing or invalid token |
| 404 | Webhook or alert ID not found |
| 422 | isGlobal is false and alertIds is empty, or alertIds contains more than 50 entries |
Authorizations
JWT Bearer token obtained from POST /api/v2/authentication/token/api-key.
Lifetime: ~24 hours (86,399 seconds). Cache the token and reuse it. Re-authenticate 5 minutes before expiry.
Scoping: API key tokens are scoped to the company the key belongs to and may restrict access to a vehicle allowlist and/or action set (see token claims).
No refresh endpoint — re-authenticate with your API key when the token expires.
Path Parameters
Body
application/json
Response
Successful response