curl --request PATCH \
--url 'https://api.scanova.io/lead/notification/12/' \
--header 'Authorization: YOUR_API_KEY' \
--header 'Content-Type: application/json' \
--data '{ "is_active": false }'
{
"id": 12,
"name": "Weekly Trade Show Report",
"to": "sales@example.com",
"cc": "manager@example.com",
"bcc": null,
"frequency": 3,
"frequency_display": "Once a Week",
"lead_list": [{ "lead_list_name": "Trade Show Signup", "lead_list_id": "L9c2f4a1e" }],
"is_active": false,
"slack_workspace": null,
"slack_channel_ids": null,
"created_by": { "id": 41, "email": "you@example.com" },
"created": "2026-09-08T10:05:00+05:30",
"modified": "2026-09-08T11:30:00+05:30"
}
Lead Notifications
Update a lead notification
PATCH /lead/notification//
PATCH
/
lead
/
notification
/
{pk}
/
curl --request PATCH \
--url 'https://api.scanova.io/lead/notification/12/' \
--header 'Authorization: YOUR_API_KEY' \
--header 'Content-Type: application/json' \
--data '{ "is_active": false }'
{
"id": 12,
"name": "Weekly Trade Show Report",
"to": "sales@example.com",
"cc": "manager@example.com",
"bcc": null,
"frequency": 3,
"frequency_display": "Once a Week",
"lead_list": [{ "lead_list_name": "Trade Show Signup", "lead_list_id": "L9c2f4a1e" }],
"is_active": false,
"slack_workspace": null,
"slack_channel_ids": null,
"created_by": { "id": 41, "email": "you@example.com" },
"created": "2026-09-08T10:05:00+05:30",
"modified": "2026-09-08T11:30:00+05:30"
}
Updates a lead report notification.
Both
Requires a Management API key with
MANAGEMENT_API (or MANAGEMENT_API_SANDBOX) quota, and the LEAD_GENERATION_EMAIL_REPORT_CAN_CREATE_UPDATE permission, sent as the raw Authorization header value — see the Management API overview.PUT https://api.scanova.io/lead/notification/{pk}/
PATCH https://api.scanova.io/lead/notification/{pk}/
integer
required
The notification’s
id.string
Internal name.
string
Recipient email address(es).
string
CC email address(es).
string
BCC email address(es).
integer
One of the
key values from List lead notification frequencies.array
Replaces the full set of
lead_ids this notification reports on.boolean
Enable or disable the notification.
curl --request PATCH \
--url 'https://api.scanova.io/lead/notification/12/' \
--header 'Authorization: YOUR_API_KEY' \
--header 'Content-Type: application/json' \
--data '{ "is_active": false }'
{
"id": 12,
"name": "Weekly Trade Show Report",
"to": "sales@example.com",
"cc": "manager@example.com",
"bcc": null,
"frequency": 3,
"frequency_display": "Once a Week",
"lead_list": [{ "lead_list_name": "Trade Show Signup", "lead_list_id": "L9c2f4a1e" }],
"is_active": false,
"slack_workspace": null,
"slack_channel_ids": null,
"created_by": { "id": 41, "email": "you@example.com" },
"created": "2026-09-08T10:05:00+05:30",
"modified": "2026-09-08T11:30:00+05:30"
}
PUT and PATCH are supported. 404 if pk isn’t a notification created by the calling user.
Related
- Retrieve a lead notification — view before updating.
- Delete a lead notification — 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
Notification updated.
Was this page helpful?