> ## Documentation Index
> Fetch the complete documentation index at: https://docs.scanova.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Validate QR Code content

> POST /qr/validate-info/

Dry-runs an `info` payload against a category's JSON schema, without creating anything.

```
POST   https://api.scanova.io/qr/validate-info/
Authorization: 401f7ac837da42b97f613d789819ff93537bee6a
```

<Note>
  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](/api-reference/management-api/qr/create) once.
</Note>

<ParamField body="info" type="string" required>
  The candidate content, as a JSON-encoded string.
</ParamField>

<ParamField body="category" type="integer" required>
  Primary key of the category whose schema to validate against.
</ParamField>

<RequestExample>
  ```bash cURL theme={null}
  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
    }'
  ```
</RequestExample>

<ResponseExample>
  ```json 200 OK theme={null}
  "valid"
  ```
</ResponseExample>

A failure returns `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](/api-reference/management-api/qr/create) — the endpoint this pre-validates for.
* [List QR categories](/api-reference/management-api/qr/category-list) — pick the `category` to validate against.
* [Update a QR Code](/api-reference/management-api/qr/update) — the same schema applies to updates and to publishing a draft.
* [QR Manager overview](/api-reference/management-api/qr/overview) — the quotas, role permissions, and Trash model shared by every endpoint in this module.
* [Management API overview](/api-reference/management-api/overview) — the auth scheme and quota rules that apply to this endpoint.


## OpenAPI

````yaml api-reference/openapi/management-api.json POST /qr/validate-info/
openapi: 3.1.0
info:
  title: Scanova Management API (v2)
  description: >-
    The complete Scanova Management API — every endpoint available at
    api.scanova.io (QR codes, folders, tags, leads, forms, analytics, plans,
    shared users & roles), plus the token-creation and usage-stats endpoints
    used to authenticate against it. Every path and request/response shape below
    was verified live against a real API key and the actual running backend
    (Phase 7, 2026-08-16) — not guessed from reading urls.py alone.
  version: 2.0.0
servers:
  - url: https://api.scanova.io
    description: Management API — QR/folder/tag/lead/form/analytics/plans endpoints
security:
  - apiKeyAuth: []
paths:
  /qr/validate-info/:
    post:
      summary: Validate QR content against a category schema
      description: >-
        Public (AllowAny) dry-run validator: checks that `info` parses as JSON
        and matches the given category's JSON schema, and runs the
        component-level quota check. No side effects — nothing is created or
        modified.
      operationId: validateQrInfo
      requestBody:
        content:
          application/json:
            example:
              info: '{"type":"url","data":{"url":"https://example.com/summer-sale"}}'
              category: 3
      responses:
        '200':
          description: The payload is valid.
          content:
            application/json:
              example: valid
        '400':
          description: >-
            Field errors describing which part of `info` failed the category's
            schema, or which component exceeds the plan's allowance.
components:
  securitySchemes:
    apiKeyAuth:
      type: apiKey
      in: header
      name: Authorization
      description: >-
        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.

````