curl -X POST "https://api.scanova.io/qr/validate-info/" \
-H "Authorization: 401f7ac837da42b97f613d789819ff93537bee6a" \
-H "Content-Type: application/json" \
-d '{
"info": "{\"type\":\"url\",\"data\":{\"url\":\"https://example.com/summer-sale\"}}",
"category": 3
}'
"valid"
QR Codes
Validate QR Code content
POST /qr/validate-info/
POST
/
qr
/
validate-info
/
curl -X POST "https://api.scanova.io/qr/validate-info/" \
-H "Authorization: 401f7ac837da42b97f613d789819ff93537bee6a" \
-H "Content-Type: application/json" \
-d '{
"info": "{\"type\":\"url\",\"data\":{\"url\":\"https://example.com/summer-sale\"}}",
"category": 3
}'
"valid"
Dry-runs an
A failure returns
info payload against a category’s JSON schema, without creating anything.
POST https://api.scanova.io/qr/validate-info/
Authorization: 401f7ac837da42b97f613d789819ff93537bee6a
This is a public endpoint (
AllowAny) and has no side effects — it neither creates nor modifies a QR Code. Use it to validate a form as the user types, then call Create a QR Code once.string
required
The candidate content, as a JSON-encoded string.
integer
required
Primary key of the category whose schema to validate against.
curl -X POST "https://api.scanova.io/qr/validate-info/" \
-H "Authorization: 401f7ac837da42b97f613d789819ff93537bee6a" \
-H "Content-Type: application/json" \
-d '{
"info": "{\"type\":\"url\",\"data\":{\"url\":\"https://example.com/summer-sale\"}}",
"category": 3
}'
"valid"
400 with per-field errors. Validation covers two things: that info matches the category’s JSON schema, and that the components it uses are within the plan’s component allowance.
Related
- Create a QR Code — the endpoint this pre-validates for.
- List QR categories — pick the
categoryto validate against. - Update a QR Code — the same schema applies to updates and to publishing a draft.
- QR Manager overview — the quotas, role permissions, and Trash model shared by every endpoint in this module.
- Management API overview — the auth scheme and quota rules that apply to this endpoint.
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
The payload is valid.
Was this page helpful?