curl --request PATCH \
--url 'https://api.scanova.io/lead/L9c2f4a1e/webhook/7/' \
--header 'Authorization: YOUR_API_KEY' \
--header 'Content-Type: application/json' \
--data '{ "url": "https://example.com/new-lead-webhook" }'
{ "id": 7, "url": "https://example.com/new-lead-webhook", "created": "2026-09-08T10:00:00+05:30", "modified": "2026-09-08T11:00:00+05:30" }
Lead Webhooks
Update a lead list webhook
PATCH /lead//webhook//
PATCH
/
lead
/
{lead_id}
/
webhook
/
{pk}
/
curl --request PATCH \
--url 'https://api.scanova.io/lead/L9c2f4a1e/webhook/7/' \
--header 'Authorization: YOUR_API_KEY' \
--header 'Content-Type: application/json' \
--data '{ "url": "https://example.com/new-lead-webhook" }'
{ "id": 7, "url": "https://example.com/new-lead-webhook", "created": "2026-09-08T10:00:00+05:30", "modified": "2026-09-08T11:00:00+05:30" }
Updates a lead list webhook’s URL.
Both
Requires a Management API key with
MANAGEMENT_API (or MANAGEMENT_API_SANDBOX) quota, and the LEAD_GENERATION_WEBHOOK_CAN_EDIT permission, sent as the raw Authorization header value — see the Management API overview.PUT https://api.scanova.io/lead/{lead_id}/webhook/{pk}/
PATCH https://api.scanova.io/lead/{lead_id}/webhook/{pk}/
string
required
The lead list’s
lead_id.integer
required
The webhook’s
id.string
required
The webhook’s new target URL.
curl --request PATCH \
--url 'https://api.scanova.io/lead/L9c2f4a1e/webhook/7/' \
--header 'Authorization: YOUR_API_KEY' \
--header 'Content-Type: application/json' \
--data '{ "url": "https://example.com/new-lead-webhook" }'
{ "id": 7, "url": "https://example.com/new-lead-webhook", "created": "2026-09-08T10:00:00+05:30", "modified": "2026-09-08T11:00:00+05:30" }
PUT and PATCH are supported. 404 if lead_id isn’t owned by this account, or pk isn’t a webhook on this lead list.
Related
- Retrieve a lead list webhook — view before updating.
- Delete a lead list webhook — remove it entirely.
- Management API overview — the auth scheme and quota architecture this endpoint is part of.
Authorizations
Send your Management API key as the raw value of the Authorization header — no "Bearer " or "Token " prefix, and no other characters. Example: Authorization: 401f7ac837da42b97f613d789819ff93537bee6a. A header containing more than one space-separated part is rejected outright. Requests also require the request's Host header to be the management API host (e.g. api.scanova.io) — the same key sent to the regular API host will not authenticate.
Response
200
Webhook updated.
Was this page helpful?