Skip to main content
Developer Platform

Build with the QRForge API

Create, manage and analyze dynamic QR codes over a modern HTTPS API. Enterprise infrastructure, predictable versioning, no surprises.

REST & JSON  ·  Scoped API keys  ·  Rate-limited by design

cURL
curl -X POST "https://api.qrforge.link/v1/qr-codes" \
-H "x-api-key: api_live_xxxxxxxxxxxxxxxxxxxxx" \
-H "Content-Type: application/json" \
-d '{
"name": "API happy path",
"redirect_url": "https://example.com/api-happy",
"type": "url"
}'
Production API
https://api.qrforge.link/v1/

Enterprise-grade QR infrastructure

Dynamic QR codes backed by Google Cloud, Cloud Run and Firestore — built for agencies, brands and high-volume campaigns.

Read the API overview

Stable, opinionated API

Clean REST endpoints for QR codes and projects, with structured error responses, cursor-based pagination and predictable versioning.

View the API reference

Analytics on the roadmap

QRForge already captures detailed scan analytics in the dashboard. Programmatic analytics endpoints ship with API v2.

See the changelog

Scoped keys & rate limits

Every API key is scoped to your account, with per-minute and per-day quotas enforced server-side to keep usage predictable.

Understand rate limits

What you can build with the QRForge API

  • Standardize every QR touchpoint across URLs, files, app deep links, Wi‑Fi, business cards and more — governed centrally and rolled out programmatically.
  • Model campaigns, clients and brands as Projects so each workspace has clear ownership, limits and analytics.
  • Treat every QR as an addressable object — resolve full metadata by ID or public slug in a single call.
  • Ship changes safely: retarget destinations and update labels without ever re‑printing physical assets.
  • Enforce hard per‑minute and per‑day quotas per user to protect the platform from abuse.
  • Measure consumption precisely with first‑class limits and usage fields on the user record.
  • Be ready for v2: analytics, BigQuery exports and webhook integrations designed for downstream data platforms.
  • Integrate from any stack — browser, backend, edge, or low‑code tools — using simple HTTPS requests.