One verification engine, three ways in
The same service that powers qrauthix.com/v/{code} is available to your own applications through a versioned REST API.
Open verification
An unauthenticated endpoint that resolves a Simple QR identifier to a verification result. No API key required — this is what browsers hit when a Simple QR is scanned.
{ "qrCode": "DEMOSIMPLEQR01" }
Device-session verification
Register a device to get a short-lived session, then call Simple or Secure verification. Secure verification additionally requires a one-time challenge and nonce, tying the result to an attested device.
POST /mobile/verify-secure
Key-authenticated management
Scoped API credentials let your backend manage products, batches, QR generation jobs, and webhook subscriptions programmatically.
Webhooks
Subscribe an HTTPS endpoint to verification events and get pushed a payload whenever a verification succeeds or fails, instead of polling. Deliveries that fail are retried with exponential backoff, up to a configurable number of attempts, before being marked dead.
Rate limiting
Public, mobile, developer, and admin traffic are isolated onto separate rate-limit tiers, so a surge of consumer scans can't starve your own integration or dashboard traffic.