> ## 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.

# Check scannability

> POST /qr/scan/check/

Runs contrast and pattern analysis on a rendered QR Code image and reports whether it is likely to scan reliably. This is what the designer uses to warn about low-contrast colour choices.

```
POST   https://api.scanova.io/qr/scan/check/
Authorization: 401f7ac837da42b97f613d789819ff93537bee6a
```

<Note>
  Public endpoint (`AllowAny`) — it analyses the image you send and stores nothing.
</Note>

<ParamField body="image" type="string" required>
  The rendered QR Code image, base64-encoded.
</ParamField>

<RequestExample>
  ```bash cURL theme={null}
  curl -X POST "https://api.scanova.io/qr/scan/check/" \
    -H "Authorization: 401f7ac837da42b97f613d789819ff93537bee6a" \
    -H "Content-Type: application/json" \
    -d '{
        "image": "data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAA..."
    }'
  ```
</RequestExample>

<ResponseExample>
  ```json 200 OK theme={null}
  {
    "is_scannable": true
  }
  ```
</ResponseExample>

## Related

* [Update a QR Code's design](/api-reference/management-api/qr/update-pattern) — save the design once it checks out.
* [Download a rendered QR Code image](/api-reference/management-api/qr/download-rendered) — turn the same rendered data into a file.
* [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/scan/check/
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/scan/check/:
    post:
      summary: Check whether a rendered QR image is scannable
      description: >-
        Public (AllowAny) contrast and pattern analysis for the QR designer
        flow. Takes a base64 image and reports whether it is likely to scan
        reliably.
      operationId: checkQrScannability
      requestBody:
        content:
          application/json:
            example:
              image: data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAA...
      responses:
        '200':
          description: Scannability verdict.
          content:
            application/json:
              example:
                is_scannable: true
        '400':
          description: '`image` missing, or not decodable as an image.'
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.

````