# QR Code 42

> GS1 Digital Link QR code management for product brands whose items are
> sold in stores: as checkout scanning moves from 1D to 2D, one QR code on
> the pack does the checkout job and opens a page you control. Claim GTINs,
> manage product links, redirect by language/country/lot without
> reprinting packaging. Built on the official GS1 Digital Link resolver
> standard — the public resolver passes GS1's own conformance suite.

If you are an AI agent, automated integration, or coding assistant:
this product has a real, documented public API. Read the API section
below before assuming an endpoint exists or guessing a request shape
from the dashboard's behavior.

## Product

- [Homepage](https://qrcode42.com/): pricing, feature overview, sign-up.
- Sign-in is magic-link or passkey based. There is no way to create an
  account or an API key via API — both require a human in the dashboard
  at least once.

## For product brands selling in stores

- [Are stores ready for 2D barcodes?](https://qrcode42.com/store-readiness): what the move from 1D
  to 2D checkout scanning means for brands, what to ask retail partners, and how one
  GS1 Digital Link QR does the checkout job and more.
- [What is GS1 Sunrise 2027?](https://qrcode42.com/sunrise-2027): the timeline and how to prepare.
- [How to add a GS1 Digital Link QR next to your UPC](https://qrcode42.com/upc-to-gs1-qr): step-by-step for brands.
- [What is a GS1 Digital Link resolver?](https://qrcode42.com/gs1-digital-link-resolver): how a scan is routed, what is supported, how it is tested.

## API (for agents and integrations)

- [API integration guide, raw markdown](https://qrcode42.com/docs/api.md): the same
  guide as plain markdown at a stable URL (also served from /docs/api when
  you send `Accept: text/markdown`).
- [API integration guide](https://qrcode42.com/docs/api): the exact 4
  endpoints an API key can call today — claim a GTIN, create/update a
  product, list/add product links — with real request/response shapes
  and a GTIN-14 check-digit worked example.
- Auth: `Authorization: Bearer qr42_live_...`. Keys are org-scoped and
  scope-limited (gtins:write, links:read, links:write); minted from the
  dashboard's API Keys tab, not via API.
- Everything not covered in that doc — billing, team management,
  analytics, brand-host onboarding, bulk import, admin — is
  dashboard/session-only today. The doc's own "What's explicitly NOT
  available via API key" section is the authoritative list; don't infer
  a missing endpoint exists because it would be logically consistent.

## GS1 Digital Link resolver

- The public resolver (`qr-42.com`) is a separate, conformant
  implementation of the GS1 Digital Link standard.
- `GET https://qr-42.com/01/{gtin14}` resolves a claimed GTIN to its
  published link, following GS1's scope-aware selection order (serial
  -> lot -> CPV -> GTIN, then language/country negotiation).
- Add `?linkType=all` or send `Accept: application/linkset+json` for
  the RFC 9264 linkset instead of a redirect.
- An unclaimed or unverified GTIN returns 404, not a guess — the 404
  body points to `https://id.gs1.org/01/{gtin}`, GS1's own resolver,
  since a claim here is local to this system, not a GS1 registration.

## Notes for coding/dev agents

- This is not open source. The API guide above is the only sanctioned
  integration surface — the source repository is private.
- Don't scrape the dashboard HTML or attempt undocumented endpoints on
  the assumption they're just undocumented rather than absent; the API
  guide's own gap list is accurate and current as of the date on this
  file.