curl --request POST \
--url 'https://api.scanova.io/lead/L9c2f4a1e/convert/' \
--header 'Authorization: YOUR_API_KEY'
{
"id": 512,
"form_id": "F3b9c1a2",
"lead_id": "L9c2f4a1e"
}
Leads & Forms
Convert a lead list to a Form
POST /lead//convert/
POST
/
lead
/
{lead_id}
/
convert
/
curl --request POST \
--url 'https://api.scanova.io/lead/L9c2f4a1e/convert/' \
--header 'Authorization: YOUR_API_KEY'
{
"id": 512,
"form_id": "F3b9c1a2",
"lead_id": "L9c2f4a1e"
}
Migrates a legacy lead list into a Form — Scanova’s current, recommended lead-capture builder.
Converting a lead list:
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.string
required
The lead list’s
lead_id. No request body.curl --request POST \
--url 'https://api.scanova.io/lead/L9c2f4a1e/convert/' \
--header 'Authorization: YOUR_API_KEY'
{
"id": 512,
"form_id": "F3b9c1a2",
"lead_id": "L9c2f4a1e"
}
- Creates a new Form from the lead list’s field definitions.
- Re-links every QR Code currently attached to the lead list to the new Form instead.
- Migrates active webhooks to the Form’s webhook mechanism (the lead list’s own webhooks are marked inactive).
- Migrates any lead notifications configured for this lead list into Form notifications.
- Marks the lead list
is_converted: true— from this point it no longer appears in List lead lists or List active lead lists, and further edits/entries/exports go through the Forms endpoints instead.
This is not idempotent in a friendly way: calling convert a second time on an already-converted lead list returns
404, since the lookup filters to non-converted lists. There is no “undo” — check is_converted (via Retrieve a lead list, which will 404 once converted) before retrying.400 under data if the transformed form data unexpectedly fails Form schema validation (a rare shape-drift edge case, not something a well-formed lead list should trigger).
Related
- List lead lists — lead lists eligible for conversion.
- Form management — where the converted resource lives afterward.
- 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
201
Converted.
Was this page helpful?