curl --request DELETE \
--url 'https://api.scanova.io/lead/notification/12/' \
--header 'Authorization: YOUR_API_KEY'
Lead Notifications
Delete a lead notification
DELETE /lead/notification//
DELETE
/
lead
/
notification
/
{pk}
/
curl --request DELETE \
--url 'https://api.scanova.io/lead/notification/12/' \
--header 'Authorization: YOUR_API_KEY'
Deletes a lead report notification.
A successful call returns
Requires an API key with
MANAGEMENT_API (or MANAGEMENT_API_SANDBOX) quota, sent as the raw Authorization header value — see the API overview.integer
required
The notification’s
id.curl --request DELETE \
--url 'https://api.scanova.io/lead/notification/12/' \
--header 'Authorization: YOUR_API_KEY'
204 No Content. 404 if pk isn’t a notification created by the calling user.
Related
- List lead notifications — see what else is configured.
- 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: YOUR_API_KEY. 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?