Machine translation without native-speaker review. The English version is binding. · Deutsch English
DurableQR integrator API · Deutsch
Dynamic QR code API · Deutsch
The API lets server-side systems create codes, read their versions, change destinations, prepare renderer parameters, export the routing map, and receive signed code-change events. · Deutsch
This page is a build-time projection of the current OpenAPI examples. It does not execute requests or accept secrets; the examples are reference text only. · Deutsch
A server-side routing surface · Deutsch
Create and list codes, read one code and its versions, change a destination with expected_version, roll back as a new version, and export the account map. The printed URL is the code URL, not the destination URL. · Deutsch
The API is designed for calls from your servers. CORS allows the panel origin, not a public browser integration, and the public page never sends the example requests. · Deutsch
Authentication and request headers · Deutsch
Create an API key in the account panel. Send its Bearer value on every request, together with a non-empty User-Agent. Create requests also require an Idempotency-Key; retry the same key with the same body when the outcome is uncertain. · Deutsch
The key is shown once when created and belongs to the panel account. Keep the placeholder in the examples as a local environment variable; never paste a real key into a public page. · Deutsch
Current request and response examples · Deutsch
The examples below are selected directly from the pinned OpenAPI document. Each block shows the method, path, status, JSON request, JSON response, and a non-executed curl command. · Deutsch
create — POST /v1/int/codes → 201 · Deutsch
{
"destination_url": "https://example.com/menu/spring",
"fallback_url": "https://example.com/menu",
"name": "Spring menu, table cards"
}{
"id": "7K4M9QXT2B",
"url": "https://qr.durableqr.com/7K4M9QXT2B"
}curl --request POST 'https://api.durableqr.com/v1/int/codes' --header 'Authorization: Bearer ${DURABLEQR_API_KEY}' --header 'User-Agent: durableqr-example/1.0' --header 'Idempotency-Key: menu-spring-202610' --header 'Content-Type: application/json' --data '{"destination_url":"https://example.com/menu/spring","fallback_url":"https://example.com/menu","name":"Spring menu, table cards"}'destination — PUT /v1/int/codes/{code_id}/destination → 200 · Deutsch
{
"expected_version": 3,
"destination_url": "https://example.com/menu/summer"
}{
"id": "7K4M9QXT2B",
"version": 4,
"destination_url": "https://example.com/menu/summer",
"fallback_url": "https://example.com/menu"
}curl --request PUT 'https://api.durableqr.com/v1/int/codes/7K4M9QXT2B/destination' --header 'Authorization: Bearer ${DURABLEQR_API_KEY}' --header 'User-Agent: durableqr-example/1.0' --header 'Content-Type: application/json' --data '{"expected_version":3,"destination_url":"https://example.com/menu/summer"}'render-spec — POST /v1/int/codes/{code_id}/render-spec → 200 · Deutsch
{}{
"id": "7K4M9QXT2B",
"params": {
"data": "https://qr.durableqr.com/7K4M9QXT2B",
"format": "png"
}
}curl --request POST 'https://api.durableqr.com/v1/int/codes/7K4M9QXT2B/render-spec' --header 'Authorization: Bearer ${DURABLEQR_API_KEY}' --header 'User-Agent: durableqr-example/1.0' --header 'Content-Type: application/json' --data '{}'pause — POST /v1/int/codes/{code_id}/pause → 200 · Deutsch
{
"expected_version": 1
}{
"id": "AAAAAAAAAA",
"state": "paused",
"version": 2
}curl --request POST 'https://api.durableqr.com/v1/int/codes/AAAAAAAAAA/pause' --header 'Authorization: Bearer ${DURABLEQR_API_KEY}' --header 'User-Agent: durableqr-example/1.0' --header 'Content-Type: application/json' --data '{"expected_version":1}'resume — POST /v1/int/codes/{code_id}/resume → 200 · Deutsch
{
"expected_version": 1
}{
"id": "AAAAAAAAAA",
"state": "active",
"version": 2
}curl --request POST 'https://api.durableqr.com/v1/int/codes/AAAAAAAAAA/resume' --header 'Authorization: Bearer ${DURABLEQR_API_KEY}' --header 'User-Agent: durableqr-example/1.0' --header 'Content-Type: application/json' --data '{"expected_version":1}'delete — DELETE /v1/int/codes/{code_id} → 200 · Deutsch
{
"expected_version": 1
}{
"id": "AAAAAAAAAA",
"state": "deleted",
"version": 2
}curl --request DELETE 'https://api.durableqr.com/v1/int/codes/AAAAAAAAAA' --header 'Authorization: Bearer ${DURABLEQR_API_KEY}' --header 'User-Agent: durableqr-example/1.0' --header 'Content-Type: application/json' --data '{"expected_version":1}'Pause, resume, and delete · Deutsch
Pause changes active to paused; resume changes paused to active. DELETE changes active, paused, grace, or frozen to deleted. A successful change creates one shared new version. Each command requires JSON with exactly expected_version, even DELETE. · Deutsch
DELETE leaves a permanent tombstone: the ID is not reused, and resume or rollback cannot restore deleted. A 503 may arrive after the tombstone commits. Cleanup can continue with the current tombstone version: success returns 200 with the same version, incomplete cleanup returns 503, a wrong version 409, and another DELETE after cleanup 404. · Deutsch
Detail does not expose the tombstone version. If you know the expected n, n+1 is only a cleanup continuation protocol, not proof of the original result or a status endpoint. A 404 proves neither who deleted the code nor that cleanup finished. · Deutsch
Paused codes redirect to fallback with 302, or show a neutral 200 without one. A fallback equal to the destination does not block access. Resume respects health and fallback; deleted returns 404 without Location. A strong META read started after commit, without a newer writer, sees the new state; DurableQR adds 0 s META cache. This is not a global time SLA and cannot revoke a Location or resource already delivered. · Deutsch
Lifecycle conflicts and retries · Deutsch
Invalid transitions return 409, blocked returns 403, deleted or absent or another owner returns 404, and unknown or damaged state returns 503. The forbidden state is checked before stale version. A stale expected_version or a competing commit returns 409; at most one new version wins. Duplicate pause or resume is 409, not a successful no-op. · Deutsch
The function returns 403 with code feature_not_entitled and message feature is not included in the account plan, or 403 with message the code cannot be changed for a blocked code. For 409 the messages are: the code cannot make this transition; expected_version does not match the current version; the code changed before this request committed; the code is frozen: it keeps its last destination; editing requires a paid account. Gateway errors have their own bodies. · Deutsch
These commands have no Idempotency-Key, response replay cache, or automatic retry. After an uncertain timeout read detail and reconcile state and version; do not retry blindly with a new version. The three route limits are shared best-effort targets of 0.005 requests/s, burst 1, not per key and not a waiting-time guarantee. · Deutsch
Access and independent retention · Deutsch
Loss of api_access blocks all three commands, including DELETE and retention cleanup, before business validation. Entitlement cache up to 30 s and API-key authorizer cache 300 s are separate, not additive. Your own access gate and retention process are needed during an outage or loss of entitlement. · Deutsch
Versions and concurrent changes · Deutsch
Destination changes and rollbacks carry expected_version. Read the code again after a retry so a write that already committed is not repeated. A rollback creates a new version; it does not rewrite the history. · Deutsch
The API response identifies the code and the resulting version. Account and route limits apply independently of the API key name. · Deutsch
Render specifications, templates, and export · Deutsch
Render-spec is read-only: it prepares a query for render.durableqr.com and does not save a design. Account design templates and the map export are separate operations with their own response shapes. · Deutsch
Use the complete response.params map when constructing a renderer URL. Do not reconstruct style fields or substitute a destination URL. · Deutsch
Signed webhooks · Deutsch
Webhooks carry code.created, code.destination_updated, and code.destination_rolled_back. Verify the HMAC-SHA256 signature over the exact raw body with the received timestamp, compare in constant time, and deduplicate the event id before returning success. · Deutsch
The full receiver algorithm and the webhook contract live in the API documentation. Delivery can duplicate or reorder events; it is not an exactly-once or seconds-level promise. · Deutsch
Limits and account offers · Deutsch
Each route has a shared best-effort rate target for all integrators together; there is no per-key rate limit. The published Pro and Business offers include API access. The offer is separate from the authorization state of a particular account. · Deutsch
API access is listed in the catalog for pro and business. · Deutsch