Skip to main content
POST
Creates a QR Code on api.scanova.io, authenticated with your raw API key — see the overview if you haven’t set that up yet.
In the dashboard you start a new QR Code in one of two ways, and the API mirrors both:
  • Quick Code — a direct-action QR Code such as a website URL, Google Maps location, App Store link, deep link, Wi-Fi, or vCard. You pick its type, fill in a few fields, and it’s created in one call.
  • Page QR Code (“Build a Page”) — a landing page built from blocks, started from a template in the gallery or from a blank canvas. It’s created as a draft and then published.
What the dashboard calls a QR Code’s type is the category field in the API. Every create call needs one — a Quick Code takes the category of the type you chose, and a Page QR Code takes the category of the template it starts from. Templates don’t replace categories; each template belongs to one.

Request fields

integer
required
The QR Code’s type, as a category id. Get the ids and slugs from List QR categories — don’t hardcode them. Set at creation only; to change it later, use Change a QR Code’s category.
string
required
dy (Dynamic) or st (Static). It must be one of the category’s allowed_qr_types, or the create fails. Page QR Codes are always dy.
string
required
The QR Code’s content, as a JSON-encoded string (not a nested object). Its shape depends on the type — see Quick Code QR Codes and Page QR Codes below.
string
Display name, up to 100 characters. If you leave it out, the category’s qr_name_pattern names the QR Code.
boolean
default:"false"
Store info as a draft instead of live content. Page QR Codes are created this way and then published — see below.
string
Dynamic only: the short-URL slug to use instead of a generated one.
integer
Dynamic only: the id of one of your verified custom domains. It’s applied only when the QR Code is created — a later update ignores it.
integer
Id of the folder to create the QR Code in.
string
Protect the QR Code’s destination with a password.
Scheduling and access fields (activate_on, expire_on, expire_on_scan_count, minimum_age, lead_list, and the geo-fencing high_accuracy_* fields) are accepted here too and behave as they do on Update.

Quick Code QR Codes

Send the category of the type and its content in one call. Look up each category id by its slug in List QR categories.
The info for each Quick Code type, before you JSON-encode it. The QR types column is what the dashboard offers for that type; the category’s allowed_qr_types is what the API enforces.
Not sure an info payload is right? Check it against the category’s schema first with Validate QR Code content.

Page QR Codes

A Page QR Code’s info is a page document — a theme plus one or more pages of blocks — and it’s only accepted through the draft-then-publish path. Creating one with that document as live info fails validation. Get the template, create a draft, then publish it:
1

Get the template

Retrieve a page template by slug (GET /page-template/{slug}/), or list them. The response carries the template’s category, theme, and blocks_json.
2

Create it as a draft

POST /qr/ with the template’s category.id, qr_type: "dy", is_draft: true, and info set to the page document built from the template (below).
3

Publish it

PATCH /qr/{qrid}/ with {"publish": true}. This validates the draft in full and makes it the live content. If validation fails, you get 400 Bad Request with the errors, and the QR Code keeps its draft unpublished.
The page document, before you JSON-encode it (12 is a placeholder — use your template’s theme.id):
To build it from a template:
  • theme_id is the template’s theme.id.
  • If blocks_json is an object with a pages array, use those pages as pages, and copy its theme_overrides and settings across.
  • If blocks_json is a plain array of blocks, wrap it as a single page: {"id":"page-1","name":"Home","type":"component","data":{"blocks": <blocks_json>}}.
A blank page works the same way: pick the category for the kind of page you want (for example, the one whose slug is restaurant), create the draft with your own blocks, and publish it.

Response

A successful create returns 201 Created with the new QR Code in the full detail shape — the same one GET /qr/{qrid}/ returns, including info and pattern_info. A draft carries its content in draft_info, with is_currently_draft: true, until you publish it. Creating a QR Code counts against the same plan limits for Dynamic and Static QR Codes as creating one in the dashboard, in addition to the MANAGEMENT_API (or INTEGRATION_ZAPIER/INTEGRATION_MCP) quota gate described in the overview.

Authorizations

Authorization
string
header
required

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

QR code created