curl --request PATCH \
--url 'https://api.scanova.io/lead/L9c2f4a1e/' \
--header 'Authorization: YOUR_API_KEY' \
--header 'Content-Type: application/json' \
--data '{ "is_active": false }'
{
"id": 205,
"lead_id": "L9c2f4a1e",
"name": "Trade Show Signup",
"is_active": false,
"usage_count": 2,
"entries_count": 14,
"linked_qrs": [
{ "qr_code__id": 88, "qr_code__qrid": "Q7f3a", "qr_code__name": "Booth QR", "qr_code__qr_type": "dy" }
],
"linked_qrs_count": 1,
"created": "2026-08-16T20:44:51.008000+05:30",
"modified": "2026-09-08T10:12:00.000000+05:30",
"data": "{\"fields\":[{\"type\":\"email\",\"label\":\"Email\",\"required\":true}]}",
"webhooks": []
}
Leads & Forms
Update a lead list
PATCH /lead//
PATCH
/
lead
/
{lead_id}
/
curl --request PATCH \
--url 'https://api.scanova.io/lead/L9c2f4a1e/' \
--header 'Authorization: YOUR_API_KEY' \
--header 'Content-Type: application/json' \
--data '{ "is_active": false }'
{
"id": 205,
"lead_id": "L9c2f4a1e",
"name": "Trade Show Signup",
"is_active": false,
"usage_count": 2,
"entries_count": 14,
"linked_qrs": [
{ "qr_code__id": 88, "qr_code__qrid": "Q7f3a", "qr_code__name": "Booth QR", "qr_code__qr_type": "dy" }
],
"linked_qrs_count": 1,
"created": "2026-08-16T20:44:51.008000+05:30",
"modified": "2026-09-08T10:12:00.000000+05:30",
"data": "{\"fields\":[{\"type\":\"email\",\"label\":\"Email\",\"required\":true}]}",
"webhooks": []
}
Updates a lead list’s name, form definition, or active state.
Both
Requires a Management API key with
MANAGEMENT_API (or MANAGEMENT_API_SANDBOX) quota, sent as the raw Authorization header value — see the Management API overview.PUT https://api.scanova.io/lead/{lead_id}/
PATCH https://api.scanova.io/lead/{lead_id}/
string
required
The lead list’s
lead_id. Immutable — it cannot be changed via this endpoint.string
Lead list name, up to 128 characters.
string
A JSON-encoded string (not a raw object) describing the lead form’s fields. Validated against the same schema used on create — malformed JSON or a schema violation returns
400 under data.boolean
Whether the form renders on the landing page.
curl --request PATCH \
--url 'https://api.scanova.io/lead/L9c2f4a1e/' \
--header 'Authorization: YOUR_API_KEY' \
--header 'Content-Type: application/json' \
--data '{ "is_active": false }'
{
"id": 205,
"lead_id": "L9c2f4a1e",
"name": "Trade Show Signup",
"is_active": false,
"usage_count": 2,
"entries_count": 14,
"linked_qrs": [
{ "qr_code__id": 88, "qr_code__qrid": "Q7f3a", "qr_code__name": "Booth QR", "qr_code__qr_type": "dy" }
],
"linked_qrs_count": 1,
"created": "2026-08-16T20:44:51.008000+05:30",
"modified": "2026-09-08T10:12:00.000000+05:30",
"data": "{\"fields\":[{\"type\":\"email\",\"label\":\"Email\",\"required\":true}]}",
"webhooks": []
}
PUT and PATCH are supported. 404 if lead_id isn’t owned by this account.
Related
- Retrieve a lead list — view current values before updating.
- Delete a lead list — remove it permanently.
- 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
Lead list updated.
Was this page helpful?