QR Code API: Create and Update Codes From Your Own Systems
A REST API for dynamic QR codes and short links — create them, repoint them, and read their scan data from whatever already runs your business.
QR Code will appear here
Select QR type
1Complete the content
2Design your QR
Choose a style
Shape Color
3Download your QR
QR Code will appear here
There is a point where QR codes stop being a design task and become part of your stack. An order needs a code on its packing slip. A new CRM record needs a code on its contact card. A generated document needs its own tracked link. None of that should involve a person opening a dashboard. The uqr.ai REST API exposes dynamic QR codes and short links as resources you can create, read, update, and delete from your own code: mint a code when a record is created, repoint it when the record changes, and pull its scan data back into your reporting on a schedule. Everything the API creates is an ordinary dynamic code — editable in the dashboard, tracked like any other, never deactivated — so an automated pipeline and a person clicking buttons produce exactly the same kind of object. If you would rather not write code, n8n covers the no-code path with the same building blocks. The API is part of the Business plan at 49 dollars a month, or 392 dollars billed annually, alongside bulk creation and custom branded domains. Full endpoint documentation, an OpenAPI specification, and a Postman collection are published. The design principle worth knowing before you integrate is that there is no separate API object model: a code created by a request is the same record as one created by a person clicking through the builder, stored the same way, visible in the same dashboard, editable by either route. That matters more than it sounds. Integrations that mint second-class objects force you to choose, permanently and early, between automation and human control — and the choice always turns out to be wrong for some subset of your codes. Here you can automate creation and still let someone fix an individual destination by hand, or prototype by hand and hand the pattern to an integration later, without migrating anything.
Six things worth automating
A contact code per record, minted automatically
When a new person is added to your CRM or directory, create their vCard code in the same step. No one designs anything, the code is on brand because the design is set once in the request, and when the record changes your integration repoints the existing code rather than issuing a new one. For any organization where people join, move, and leave continuously, this is the difference between contact codes being maintained and being abandoned.
Free vCard QR Code Generator →A tracked code on every generated document
Invoices, quotes, packing slips, and certificates are generated by software already. Calling the API as part of that generation gives each document its own code and its own scan record, so you can see which documents actually get opened and follow up on the ones that do not. Because each code is independently editable, a reissued document can point at the corrected version without changing what was already sent.
PDF to QR Code Generator →Codes created per order, per ticket, per batch
Anything with a unique identifier can carry a unique code created at the moment the identifier exists. Orders, support tickets, production batches, bookings — the API turns each one into a scannable, trackable object without a human in the loop. This is the natural upgrade from periodic bulk uploads once volume becomes continuous rather than scheduled.
Text QR Code Generator →Scan data pulled into your own reporting
Read scan data through the API and put it where the rest of your numbers live — a warehouse, a spreadsheet, a dashboard your team already opens. Codes stop being a separate tool you have to remember to check and become another source alongside everything else. On Pro, CSV export covers the same need manually; the API is for when it should happen on a schedule. The practical test is whether anyone would notice the numbers going stale. A metric that lives in a tool nobody opens is a metric that quietly stops informing decisions, and print campaigns are especially prone to this because the feedback loop is already long. Pulling scan data into the reporting your team reads anyway is usually what turns QR codes from an experiment somebody ran into a channel with an owner.
Location QR Code Generator →Branding applied by the machine, not by hand
Colors, logo, and frame are parameters on the request, so every programmatically created code comes out matching your brand without anyone opening a design tool. That consistency is much easier to hold at scale through an API than through a process that depends on people remembering the hex codes.
QR Code with Logo Generator →No-code automation with n8n
If the work does not justify writing an integration, n8n connects uqr.ai to other systems visually: a trigger somewhere else, a code created or updated here. It uses the same API underneath, so anything you prototype in a no-code flow can be moved into your own code later without changing how the codes behave. That makes it a reasonable first step even when you expect to write a real integration eventually — build the flow visually, confirm the shape of the problem is what you assumed, then port it once the volume or the logic justifies the engineering time. To be precise about what exists: the REST API and n8n are the two supported automation routes, and both are documented.
File to QR Code Generator →How to use the QR code API
- 1
Create an API key
Generate a key from your API settings. Keys authenticate every request and can be revoked without affecting the codes they created.
- 2
Read the endpoint documentation
Endpoints for QR codes and short links are documented publicly, with an OpenAPI specification and a Postman collection if you would rather explore than read.
- 3
Create your first code with a request
Post a destination and a type and you get back a dynamic code with its own short link — the same object the dashboard would have produced.
- 4
Wire it into the system that should own it
Create codes where the underlying record is created, update them when it changes, and read scan data back on whatever schedule your reporting runs on.
API codes are ordinary codes
Anything created programmatically shows up in the dashboard, is editable by hand, and reports scans like every other code. There is no second-class API object.
Documented properly
Public endpoint documentation, an OpenAPI specification, and a Postman collection, so integrating does not depend on guessing or on support answering questions.
A no-code path too
n8n covers automation for people who do not want to write an integration, using the same API underneath.
Frequently asked questions
Which plan includes the API?+
Business, at 49 dollars a month or 392 dollars billed annually. Bulk creation and custom branded domains are on the same tier. Lite and Pro do not include API access.
What can the API do?+
Create, read, update, and delete dynamic QR codes and short links, apply design options, set link options such as password protection and expiry, and read scan data. In practice, everything you would do in the dashboard for a code you own.
Are codes created through the API editable in the dashboard?+
Yes. They are the same objects. A code minted by an integration can be edited by a person, and a code made by hand can be updated by your integration.
Is there a no-code option?+
Yes — n8n. It connects uqr.ai to other systems through a visual builder rather than code, and runs on the same API, so behaviour is identical.
How do I get started?+
Create an API key in your API settings, then work through the public endpoint documentation. The OpenAPI specification and Postman collection are the fastest way to make a first successful request.
How should I handle API keys safely?+
Keep them server-side. A key belongs in your backend or your automation platform's credential store, never in client-side JavaScript, a mobile app bundle, or a committed configuration file — anything shipped to a browser or a device is readable by anyone who wants to read it. Use a separate key per integration so you can revoke one without disturbing the others, and revoke immediately rather than rotating slowly if a key is ever exposed. Revoking a key never affects the codes it created; they carry on resolving normally.
What happens to API-created codes if I change plan?+
They keep resolving. Codes are never deactivated regardless of plan, so anything already printed is safe. API access itself is a Business capability, so creating or updating codes programmatically requires an active Business plan — the existing codes stay, but the integration stops being able to mint new ones.
Put QR codes in your pipeline instead of your to-do list. See the Business plan.