curl --request DELETE \
--url 'https://api.scanova.io/lead/L9c2f4a1e/webhook/7/' \
--header 'Authorization: YOUR_API_KEY'
Lead Webhooks
Delete a lead list webhook
DELETE /lead//webhook//
DELETE
/
lead
/
{lead_id}
/
webhook
/
{pk}
/
curl --request DELETE \
--url 'https://api.scanova.io/lead/L9c2f4a1e/webhook/7/' \
--header 'Authorization: YOUR_API_KEY'
Deletes a lead list webhook.
A successful call returns
Requires a Management API key with
MANAGEMENT_API (or MANAGEMENT_API_SANDBOX) quota, and the LEAD_GENERATION_WEBHOOK_CAN_DELETE permission, sent as the raw Authorization header value — see the Management API overview.string
required
The lead list’s
lead_id.integer
required
The webhook’s
id.curl --request DELETE \
--url 'https://api.scanova.io/lead/L9c2f4a1e/webhook/7/' \
--header 'Authorization: YOUR_API_KEY'
204 No Content. 404 if lead_id isn’t owned by this account, or pk isn’t a webhook on this lead list.
Related
- List lead list webhooks — see what else is configured.
- 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
204
Deleted.
Was this page helpful?