Render a QR code
Styled, optionally logo-bearing QR codes, drawn natively and verified before delivery: every response is decoded and compared to data on the way out. A code that would not scan is a 422 unscannable and nothing is counted - the guarantee is the feature.
A logo forces the highest error-correction level and is composited over the center on a knockout tile (logo_pad). Send it inline as a data: URI (logo) or by URL (logo_url); remote logos face the same target guard and rate caps as screenshot URLs.
QRs are deterministic, so identical requests hit the cache and cache hits count nothing. Each code counts one render.qr, a free utility: it shows in usage and is never charged. Output never carries a badge - a mark inside a scannable symbol would corrupt it.
To place a QR inside a stored template render, use the qr object on POST /v1/image/{id} instead - each entry becomes a {{qr.<name>}} variable holding a data URI.
Request
- Base URL: https://api.ironfang.com/render
- URL: https://api.ironfang.com/render/v1/qr
- Auth: HTTP bearer
Headers
Makes a synchronous render happen, and count, at most once. Any string up to 255 characters, remembered per account. The first request under a key is admitted and rendered as usual; a synchronous result is not kept, so the same request again under the key is a 409 idempotency_key_used and reserves nothing - send a new key to render again. A different request under a used key is a 409 idempotency_conflict. An identical request inside the cache window is still served from cache.
Request body
Response
The rendered image. png unless format: jpeg was requested.
Changes
No recorded changes to this operation across all 1 revision of this API.