Skip to main content
The Scanova API is the programmatic interface to your Scanova account. Anything you can do in the dashboard — create a QR Code, move it between folders, read a form response, pull scan analytics — you can do over HTTP from your own application.

Base URL

Every endpoint in this tab lives on one host, and takes an API key as the raw Authorization header value:
Send the key on its own. It is not a bearer token, so no Bearer or Token prefix.
Responses are JSON. Paths end in a trailing slash; leaving it off returns a 301 to the slashed form rather than the resource, so send the slash.

What you can manage

QR Codes

Create, read, update, download, and delete QR Codes, plus health checks and bulk operations

Folders & tags

Organize codes into folders, apply shared or custom tags, and manage custom domains and themes

Leads & forms

Build forms, read and export responses, manage lead lists, and route submissions to webhooks

Analytics

Scan totals, geography, devices, and languages, with raw scan export for your own warehouse
Shared users and roles, the media library, activity logs, payments, and the Zapier, HubSpot, and Slack integrations are all covered too — see the sidebar for the complete list.

Before your first call

  • A Scanova account you can Log In to
  • An API key, generated from Developer → API in the dashboard — see Creating & managing API keys
  • A backend or admin tool that can send HTTPS requests and keep a secret off the client
An API key acts on your live account. There is no separate test environment, so a key labeled sandbox reads and writes the same real QR Codes, folders, and leads as any other key.

Elsewhere in the docs

Three things sit outside this tab and are easy to confuse with it:

Next steps

API overview

Key environments, the rules every endpoint follows, and what to check when a call returns 401

List QR Codes

GET /qr/ — the endpoint most integrations start with
Something not behaving as documented? Email support@scanova.io or search the Help Center.