canonical: https://jentic.com/apis/linqr.app/linqr

# Linqr App LinQR

LinQR is a QR Code generation API that produces visually customised codes for text, email, WiFi credentials, contact cards, cryptocurrency payments, phone numbers, SMS, and geolocation. The platform supports batch generation for high-volume workflows, custom embedded image management for branded codes, and two authentication paths (direct OAuth2 or RapidAPI proxy). Maximum request size is 32MB and request timeout is 180 seconds, supporting designs that include large background images.

## For AI agents

Generate branded QR codes for text, contact, WiFi, payment, geo, and SMS payloads, with batch generation and custom embedded images for marketing and operations use cases.

## Scope

Does not handle QR scan analytics, link redirection, or barcode formats other than QR - use for QR code image generation only.

## Capabilities

- Generate QR codes for text, email, WiFi, contact, crypto, phone, SMS, geo, or arbitrary payloads via /qrcode/* endpoints
- Produce QR codes in batches via POST `/batch/qrcode` for catalogue or campaign rollouts
- Upload, list, and delete custom embedded images via /images endpoints to brand QR codes with logos
- Authenticate via OAuth2 client credentials directly or via the RapidAPI X-RapidAPI-Key proxy
- Tune large designs within a 32MB request size and 180-second timeout for image-heavy batch jobs

## Use cases

### Branded Marketing QR Codes

Generate branded QR codes for marketing collateral, packaging, and print campaigns by uploading a logo image and embedding it in every code. The /images endpoints manage the logo library and the /qrcode endpoints reference an image id when creating each code. Suitable for marketing teams producing thousands of codes per campaign with consistent branding.

Example prompt: POST /images with the brand logo, then POST /qrcode with content=https://example.com/promo and the image id to produce a branded code.

### WiFi and Contact Sharing

Produce QR codes that join a WiFi network or save a contact card on scan, useful for event venues, hotels, and conference badges. POST `/qrcode/wifi` accepts SSID, password, and security type, while POST `/qrcode/contact` accepts vCard fields. Both return ready-to-print images sized for badges or signage.

Example prompt: POST `/qrcode/wifi` with ssid=GuestNet, password=hello123, encryption=WPA2 and download the returned image for printing on event signage.

### Bulk QR Generation for Catalogues

Generate hundreds or thousands of QR codes in a single call for product catalogues, asset tags, or ticketing systems. POST `/batch/qrcode` accepts a list of payloads and returns all generated images in one response, removing the need to orchestrate per-item requests. Best for one-off catalogue rollouts or seasonal campaign drops.

Example prompt: POST `/batch/qrcode` with an array of product URLs and persist each returned image with its product SKU.

### AI Agent Code Generation

Let an AI agent produce a QR code on demand inside a chat, document, or workflow without surfacing OAuth client credentials. Through Jentic, the agent searches for the LinQR generate operation, loads the schema, and executes the right /qrcode/* endpoint while credentials stay isolated in your Jentic One instance. The returned image can be inlined in chat or attached to a generated document.

Example prompt: Search Jentic for 'generate a QR code for a URL', load the schema, execute POST /qrcode with content=<user URL>, and return the image.

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/qrcode` | Generate a QR code for arbitrary content |
| POST | `/qrcode/wifi` | Generate a WiFi QR code |
| POST | `/qrcode/contact` | Generate a contact (vCard) QR code |
| POST | `/batch/qrcode` | Batch generate multiple QR codes |
| POST | `/images` | Upload an embedded brand image |
| GET | `/images` | List embedded images |

## Key resources

- **Single QR Code** — Per-payload QR generation via /qrcode endpoints (text, email, wifi, contact, crypto, phone, sms, geo)
- **Multiple QR Codes** — Batch QR generation via POST `/batch/qrcode` for catalogue and campaign rollouts
- **Image management** — Upload, list, and delete embedded brand images via /images and `/images/{id}`

## Why Jentic

- **Setup:** Wiring LinQR by hand means running its OAuth2 client-credentials flow against api.linqr.app to exchange a client id and secret for short-lived tokens, or managing a RapidAPI key, and handling retries yourself. Through Jentic you install once, import LinQR from the API Directory, store the client credentials once, and your agent calls it.
- **Permission scoping:** LinQR takes the QR content in the request body rather than a resource id in the URL path, so limit the agent to the operations it needs, such as POST /qrcode or POST `/qrcode/wifi.` You choose the operations it may call, so image management like DELETE on uploaded images is not included unless you add it.
- **Credential handling:** Your LinQR client secret or RapidAPI key is stored once, encrypted, by your own Jentic One instance and exchanged for a short-lived token at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'generate a WiFi QR code' or 'create a batch of QR codes', and Jentic returns the matching LinQR operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **GoQR API** — Simple QR code generator with no auth and basic styling options
- **Urlbox API** — Screenshot rendering API that pairs with QR codes for marketing collateral
- **Linkly API** — Short link and click analytics platform - point QR codes at trackable URLs

## FAQ

### What authentication does the LinQR API use?

LinQR supports two schemes. OAuth2 client credentials are the recommended path for direct access via api.linqr.app. The RapidAPI proxy at qrcode3.p.rapidapi.com accepts an X-RapidAPI-Key header instead. Through Jentic, either credential set is stored in your Jentic One instance and injected at execution time.

### Can I generate QR codes for WiFi or contact cards with LinQR?

Yes. POST `/qrcode/wifi` accepts SSID, password, and security type. POST `/qrcode/contact` accepts vCard-style fields (name, phone, email). Both return image bytes ready to print, no client-side composition needed.

### What are the request size and timeout limits for the LinQR API?

Maximum request size is 32MB and request timeout is fixed at 180 seconds. These limits matter most for `/batch/qrcode` jobs and for /images uploads when embedding large brand logos in codes.

### How do I generate a branded QR code through Jentic?

Run pip install jentic, then upload a brand image once via POST /images. Search Jentic for 'generate a branded QR code', load the POST /qrcode schema, supply the image id with the QR payload, and execute. The returned image bytes can be saved or inlined directly.

### Can LinQR produce QR codes in bulk?

Yes. POST `/batch/qrcode` accepts an array of payloads in one call and returns the generated images together, which avoids per-item HTTP overhead. Keep total request size under 32MB and the job under 180 seconds - split very large catalogues into multiple batches.

### Can I limit what my agent is allowed to do with the LinQR API?

Yes. Because you self-host Jentic One, your own rules decide which LinQR operations and credentials the agent may use, so you can allow only the generation calls it needs, such as POST /qrcode or POST `/qrcode/wifi`, and leave everything else out. LinQR takes the QR content in the request body rather than a resource id in the URL path, so scoping is done per operation rather than per record. Image management such as DELETE on uploaded brand images stays unavailable to the agent unless you explicitly add it. The stored client secret or RapidAPI key is injected only at execution time and never reaches the agent's prompt or logs.