QR Code API: how to integrate generation into your web app

The codigo-qr.es API has two tiers.

Public endpoint (no account needed):

`POST /api/v1/qr/render` generates a static QR and returns the image in base64. Limit: 50 requests per day per IP.

Pro endpoints (require API key):

| Method | Path | Purpose | |--------|------|---------| | `GET` | `/api/v1/qr` | List all your QR codes | | `POST` | `/api/v1/qr` | Create a static or dynamic QR | | `GET` | `/api/v1/qr/{id}` | Get QR details | | `PATCH` | `/api/v1/qr/{id}` | Update destination or name | | `DELETE` | `/api/v1/qr/{id}` | Delete a QR | | `GET` | `/api/v1/qr/{id}/image` | Download PNG or SVG image | | `GET` | `/api/v1/qr/{id}/stats` | Scan statistics |

All Pro responses follow `{ "data": {...}, "error": null }`. On error, `data` is null and `error` contains `code` and `message`.

Step 1. Create an account at codigo-qr.es.

Step 2. Activate the Pro plan. The full API is Pro-exclusive at €5.99/month.

Step 3. Go to /panel/account and click Generate API key. The token is shown only once. Save it in a password manager or environment variable.

Add this header to every request:

```bash curl https://codigo-qr.es/api/v1/qr \ -H "Authorization: Bearer cqr_your_token_here" ```

If the key is invalid or the plan has expired, the API returns `401 UNAUTHORIZED` or `403 PLAN_REQUIRED`. You can revoke the key at any time from the dashboard; it stops working immediately.

The public endpoint is the fastest way to test the API or generate simple QR codes from a script without managing authentication:

```bash curl -X POST https://codigo-qr.es/api/v1/qr/render \ -H "Content-Type: application/json" \ -d '{"value":"https://yourdomain.com","format":"png","size":512}' ```

Parameters:

- `value` (required): the QR content. Can be a URL, text, email, WiFi data...
• `format`: `"png"` (default) or `"svg"`
• `size`: `256`, `512` (default) or `1024`

The response returns the image in base64 inside a JSON envelope:

```json { "data": { "image": "iVBORw0KGgo...", "format": "png", "size": 512 }, "error": null } ```

If you exceed 50 requests per day from the same IP, you get `429 RATE_LIMITED` with the `Retry-After` header indicating when the counter resets.

A dynamic QR encodes a fixed short URL (`/r/{slug}`) but its final destination can be changed whenever you want. The printed code never changes.

Create a dynamic QR:

```bash curl -X POST https://codigo-qr.es/api/v1/qr \ -H "Authorization: Bearer cqr_your_token" \ -H "Content-Type: application/json" \ -d '{ "label": "May restaurant menu", "type": "url", "value": "https://yourrestaurant.com/menu-may", "is_dynamic": true, "tracking_mode": "redirect" }' ```

Change the destination without reprinting:

```bash curl -X PATCH https://codigo-qr.es/api/v1/qr/{id} \ -H "Authorization: Bearer cqr_your_token" \ -H "Content-Type: application/json" \ -d '{"destination": "https://yourrestaurant.com/menu-june"}' ```

Download the QR image:

```bash curl -o my-qr.png \ "https://codigo-qr.es/api/v1/qr/{id}/image?format=png&size=1024" \ -H "Authorization: Bearer cqr_your_token" ```

View scan statistics:

```bash curl "https://codigo-qr.es/api/v1/qr/{id}/stats?period=30d" \ -H "Authorization: Bearer cqr_your_token" ```

The API is the right tool when volume or automation make it impractical to generate QR codes manually from the dashboard.

E-commerce: QR codes on delivery notes and invoices

The ERP generates the delivery note PDF. With a call to `POST /api/v1/qr`, it gets a QR pointing to the order tracking URL. If the URL changes, `PATCH /api/v1/qr/{id}` updates the destination without regenerating or reprinting anything.

Restaurants: table menu from the POS

The POS creates a QR per table when the shift opens. It points to the day's menu, which the chef updates in the CMS. The QR on the table never changes; the destination does. No more laminating new menus every week.

Events: personalized tickets in bulk

A ticketing system generates a unique QR per ticket with `POST /api/v1/qr` and embeds it in the PDF. At the door, the scanner verifies the QR by reading `GET /api/v1/qr/{id}` to confirm it is valid.

Logistics: packages with tracking

Each package gets a QR pointing to its tracking page. The customer scans from the envelope and sees the delivery status in real time. Scans are logged in `GET /api/v1/qr/{id}/stats`.

The API applies rate limits to ensure availability for all users.

Public tier (`/api/v1/qr/render`):
• Limit: 50 requests per day per IP
• Window: 24 hours
• No registration required

Pro tier (endpoints with API key):
• Limit: 60 requests per minute per user
• No daily total limit

When you exceed the limit, the API returns `429 Too Many Requests` with these headers:

``` X-RateLimit-Limit: 60 X-RateLimit-Remaining: 0 X-RateLimit-Reset: 1747612800 Retry-After: 43 ```

See the full API documentation for all parameters and error responses.