How often your QR codes are scanned, by code and by design, with scan history.
How often your QR codes are scanned, by code and by design, with scan history.
Prerequisites
- A bearer token in the
Authorizationheader. Any endpoint that needs no token says so on its own page. - The id of each record the call targets. Every endpoint page lists the ids it needs.
Errors
| Status | Meaning |
|---|---|
401 | The bearer token is missing, expired or invalid |
403 | The token is valid but the record sits outside your account |
404 | Returned if the template does not belong to the authenticated user's company |
422 | The request failed validation — the response names the fields |
500 | Unexpected server error |
Individual endpoints may return more; each page lists its own.
Endpoints
| Method | Endpoint | Description |
|---|---|---|
GET | Scans by QR code | Get aggregate QR code counts for the authenticated account-user's company: total, a breakdown by destination type, and a count of those created in the last 30 days. |
GET | Scans by design | Get aggregate QR template counts for the authenticated user's company — total templates, a breakdown by template type, and a count of those created in the last 30 days. |
GET | Scan history for a code | Get paginated scan history (newest first by scanned_at) for a QR code belonging to the authenticated account-user, along with a small summary of the QR code itself. |
GET | Scan history for a design | Get paginated scan-history records for a QR code template (by path ID), newest first by scanned_at, alongside a minimal template stub; 404s if the template does not belong to the authenticated user's company. |