QRCode SuiteQR platform
Developers

QR code API for developers

QRCode Suite exposes a versioned REST API on the platform: create QR codes, re-point destinations, and read scan analytics with the same engine the dashboard uses. Authentication uses scoped API keys you mint in the dashboard. It also records conversions at /api/v1/conversions, sends HMAC-signed webhooks for scans and form leads, and ships a JavaScript pixel for on-site conversions.

API access is included on the Business and Agency plans.

Start free →See pricing

QR code CRUD endpoints

List and create QR codes at /api/v1/qrcodes; read, update and delete one at /api/v1/qrcodes/:id. Changing destination_url or status via PATCH takes effect on the very next scan — the printed code never changes.

Scoped API keys

Mint API keys from the dashboard with only the scopes they need — qrcodes:read, qrcodes:write, scans:read, conversions:write. Each key is rate-limited to 300 requests a minute on the REST API, plus a separate 300 a minute on conversions, and bound to one workspace; keep it server-side.

Scan data over the API

Page through scan events at /api/v1/scans, filtered by qr_id and a number of days: device, country, referrer and timestamp — the same privacy-first data the dashboard charts, with no raw IPs anywhere.

Conversion API

POST purchase and signup events to /api/v1/conversions with an event_name, an external_id for deduplication, an optional amount and currency, and the qr_slug that brought the customer, to attribute revenue back to the scan.

Webhooks

Subscribe endpoints to qr.scanned (every real, non-bot scan) and qr.lead_captured (every hosted-form lead). Deliveries are HMAC-signed and retried with backoff.

JavaScript pixel

A lightweight pixel (/pixel.js) posts on-site conversions to /api/collect and links them to the QR scan that brought the visitor through a first-party attribution reference (the qr_ref parameter on the destination link, kept in your site’s localStorage). No fingerprinting; with Do Not Track on it sends the conversion without any custom properties; and it matches the platform’s no-raw-IP privacy model.

Endpoints in practice

Requests are JSON in, JSON out, authenticated with a Bearer API key.

curl -X POST https://qrcode-suite.com/api/v1/qrcodes \
  -H "Authorization: Bearer $QRCS_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "type": "dynamic_url",
    "name": "Spring packaging insert",
    "destination_url": "https://example.com/spring-landing"
  }'
# Re-point a printed code — no reprint needed
curl -X PATCH https://qrcode-suite.com/api/v1/qrcodes/$QR_ID \
  -H "Authorization: Bearer $QRCS_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "destination_url": "https://example.com/summer-landing" }'
curl -X POST https://qrcode-suite.com/api/v1/conversions \
  -H "Authorization: Bearer $QRCS_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "event_name": "purchase",
    "external_id": "order-1042",
    "amount": 49.90,
    "currency": "EUR",
    "qr_slug": "k7Qm2x"
  }'

Render the image as PNG or SVG

GET /api/qr/:slug returns the scannable image of a code you created: ?format=png or ?format=svg, and ?size= in pixels (400 by default). For print, ?dpi= (150, 300, 600 or 1200) with ?mm= gives a file physically that many millimetres wide, with the density written into the PNG so layout software places it at the right size. The file extension follows what was actually rendered, so a design the raster path cannot flatten comes back as SVG and says so. The endpoint needs no API key — the image shows nothing beyond the slug already printed on the code — and it is rate-limited per hashed IP. It only renders codes that exist in a workspace; it is not an anonymous generator.

# Screen image — no API key needed
curl -o insert.png "https://qrcode-suite.com/api/qr/k7Qm2x?format=png&size=600"

# Print file: 25 mm wide at 300 DPI
curl -o insert-print.png "https://qrcode-suite.com/api/qr/k7Qm2x?format=png&dpi=300&mm=25"

Running the WordPress plugin?

The WordPress plugin has its own REST routes on your site, under /wp-json/qrcode-suite/v1/, authenticated with keys minted in the plugin admin (Authorization: Bearer or X-API-Key). It also adds a wp qrcs command for WP-CLI with create, scan-stats, bulk-export, webhook-test and label-generate. Those routes act on the codes stored in WordPress; the platform API above acts on your workspace. Linking the site to the platform (opt-in) mirrors its codes, daily scan totals and WooCommerce conversions into your dashboard.

Frequently asked questions

What is QRCode Suite?

QRCode Suite is a standalone QR code platform: create a free account and generate branded, dynamic QR codes in the browser — no WordPress required. Connectors bring the same codes to WordPress and WooCommerce, where orders can be attributed to specific QR codes.

Does QRCode Suite work without WordPress?

Yes. QRCode Suite is a standalone SaaS — sign up, create QR codes, and track scans entirely on qrcode-suite.com. The WordPress plugin is an optional connector that brings your codes into wp-admin and adds WooCommerce order attribution.

Does QRCode Suite require a separate subscription?

The Free plan is available at no cost — no credit card required. Paid plans (Pro €9, Business €29, Agency €79 per month) unlock unlimited codes, redirect rules, and more. There is no separate per-scan fee.

What QR code types does QRCode Suite support?

QRCode Suite supports 22 QR code types: Static URL, Dynamic URL, Plain Text, Phone, Email, Location, Link Hub, SMS, WhatsApp, Wi-Fi, vCard, Social profile, PDF, File download, App download, Coupon, Calendar event, Lead capture form, Review collection, Wholesale inquiry, Loyalty reward, and Custom payload.

Can I change the destination of a QR code after printing it?

Yes. Dynamic QR codes use a short redirect URL. You can update the destination from your dashboard at any time without generating or reprinting the code.

Is QRCode Suite GDPR-compliant?

QRCode Suite is built with GDPR in mind: raw IP addresses are never stored — visitors are counted with keyed hashes — bot traffic is filtered automatically, and scan events are purged once your plan retention window elapses. Consult your legal team for your specific obligations.

Build on the QRCode Suite API

Scoped API keys and REST endpoints — included on Business and above.

Get Business PlanRead documentation