curl --request POST \
--url 'https://api.scanova.io/lead/' \
--header 'Authorization: YOUR_API_KEY' \
--header 'Content-Type: application/json' \
--data '{
"name": "Trade Show Signup",
"data": "{\"fields\":[{\"type\":\"email\",\"label\":\"Email\",\"required\":true}]}"
}'
{
"id": 205,
"lead_id": "L9c2f4a1e",
"name": "Trade Show Signup",
"created": "2026-08-16T20:44:51.008000+05:30",
"is_active": true,
"usage_count": 0,
"entries_count": 0,
"linked_qrs": [],
"modified": "2026-08-16T20:44:51.008000+05:30",
"data": "{\"fields\":[{\"type\":\"email\",\"label\":\"Email\",\"required\":true}]}",
"webhooks": []
}
Leads & Forms
Create a lead list
POST /lead/
POST
/
lead
/
curl --request POST \
--url 'https://api.scanova.io/lead/' \
--header 'Authorization: YOUR_API_KEY' \
--header 'Content-Type: application/json' \
--data '{
"name": "Trade Show Signup",
"data": "{\"fields\":[{\"type\":\"email\",\"label\":\"Email\",\"required\":true}]}"
}'
{
"id": 205,
"lead_id": "L9c2f4a1e",
"name": "Trade Show Signup",
"created": "2026-08-16T20:44:51.008000+05:30",
"is_active": true,
"usage_count": 0,
"entries_count": 0,
"linked_qrs": [],
"modified": "2026-08-16T20:44:51.008000+05:30",
"data": "{\"fields\":[{\"type\":\"email\",\"label\":\"Email\",\"required\":true}]}",
"webhooks": []
}
Lead lists are Scanova’s original lead-capture feature — a form definition (
data) attached to a QR Code’s landing page. List or create them here.
Lead Lists are a legacy feature. Scanova’s dashboard now steers new lead-capture use cases toward Forms instead, which cover the same “collect visitor data from a QR Code scan” use case with a more capable builder. Existing lead lists keep working, and this endpoint is unaffected, but build new integrations against Forms unless you specifically need to manage a pre-existing lead list.
Requires an API key with
MANAGEMENT_API (or MANAGEMENT_API_SANDBOX) quota, sent as the raw Authorization header value — see the API overview.curl --request POST \
--url 'https://api.scanova.io/lead/' \
--header 'Authorization: YOUR_API_KEY' \
--header 'Content-Type: application/json' \
--data '{
"name": "Trade Show Signup",
"data": "{\"fields\":[{\"type\":\"email\",\"label\":\"Email\",\"required\":true}]}"
}'
{
"id": 205,
"lead_id": "L9c2f4a1e",
"name": "Trade Show Signup",
"created": "2026-08-16T20:44:51.008000+05:30",
"is_active": true,
"usage_count": 0,
"entries_count": 0,
"linked_qrs": [],
"modified": "2026-08-16T20:44:51.008000+05:30",
"data": "{\"fields\":[{\"type\":\"email\",\"label\":\"Email\",\"required\":true}]}",
"webhooks": []
}
string
required
Lead list name, up to 128 characters.
string
required
A JSON-encoded string (not a raw object) describing the lead form’s fields. Validated against the same lead-form schema the dashboard’s lead-list builder uses — malformed JSON or a schema violation returns a 400 under
data.boolean
default:"true"
Whether the form renders on the landing page.
The response includes
data and webhooks (a list of {id, url, created, modified} notification webhooks) — fields only present on the detail shape returned by create/retrieve, not on the list endpoint above.Related
- List lead lists — the other operation on this same endpoint.
- Form management — the current, recommended lead-capture builder this legacy feature is being steered toward.
- 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
201
Lead list created
Was this page helpful?