curl --request DELETE \
--url 'https://api.scanova.io/forms/F8a9b0c1d2e3f4g5h/' \
--header 'Authorization: YOUR_API_KEY'
Leads & Forms
Delete a form
DELETE /forms//
DELETE
/
forms
/
{form_id}
/
curl --request DELETE \
--url 'https://api.scanova.io/forms/F8a9b0c1d2e3f4g5h/' \
--header 'Authorization: YOUR_API_KEY'
Permanently deletes a form.
A successful call returns
Like lead lists, forms are hard-deleted — there is no trash/restore step, unlike QR Codes. Deleting a form does not automatically delete its responses or unlink its QR Codes; use Bulk-delete form responses first if you also want the response data gone.
Requires a Management API key with
MANAGEMENT_API (or MANAGEMENT_API_SANDBOX) quota, and the LEAD_GENERATION_CAN_DELETE permission, sent as the raw Authorization header value — see the Management API overview.string
required
The form’s
form_id.curl --request DELETE \
--url 'https://api.scanova.io/forms/F8a9b0c1d2e3f4g5h/' \
--header 'Authorization: YOUR_API_KEY'
204 No Content. 404 if form_id isn’t owned by this account.
Related
- Retrieve a form — check contents before deleting.
- Bulk-delete form responses — remove response data separately.
- List forms — see what else exists.
- 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
204
Deleted.
Was this page helpful?