Machine translation without native-speaker review. The English version is binding. · čeština English
DurableQR destination history file v1
This private history is not a map file or a resolver routing file. It does not change map file v1. · čeština
Download and authorization
GET /v1/export/history uses the panel JWT and its verified subject. GET /v1/int/export/history uses an API key, User-Agent and the current api_access entitlement. No query parameters are accepted, including format and cursor. There is no CSV, public URL, stored dump or scheduled export. · čeština
A successful response is raw JSONL, not a JSON envelope or base64. · čeština
| Header | Value |
|---|---|
| Content-Type | application/jsonl; charset=utf-8 |
| Content-Disposition | attachment; filename="durableqr-history.jsonl" |
| X-History-File-SHA256 | lowercase SHA-256 hex of the exact body bytes |
| X-History-File-Records | decimal data-line count excluding the declaration |
| Cache-Control | no-store |
The panel origin can read the disposition, checksum and count headers. A client may save a durableqr-history.jsonl.sha256 sidecar containing the digest, two spaces, filename and LF. The backend does not store the sidecar. SHA-256 is neither a signature nor proof of completeness. · čeština
Canonical bytes and fields
UTF-8 without BOM; each line ends in LF including the last. No CR, blank lines or extra spaces between JSON tokens. Unicode and URLs are not normalized; JSON escaping remains. The first line is exactly {"format":"durableqr-history-file","format_version":1}. Each ordinary record has exactly these eight keys in this order: · čeština
| Key | Meaning |
|---|---|
| stable_id | Exactly 10 ASCII characters from 0123456789ABCDEFGHJKMNPQRSTVWXYZ |
| version | JSON integer from 1 to 9007199254740991 |
| url | Exact stored URL, http or https, at most 2048 UTF-8 bytes |
| actor | Lowercase hexadecimal UUID of the actor |
| timestamp | Exact stored timestamp; ordinary UTC uses YYYY-MM-DDTHH:MM:SS.mmmZ; billing preserves canonical UTC datetime.isoformat() precision and +00:00 |
| rolled_back_from | null or integer from 1 to version minus 1 |
| transferred_from | null or lowercase hexadecimal UUID of the sender |
| source | null or billing |
The URL scheme is ASCII-case-insensitive and needs at least one character after //; U+0000 through U+001F, backslash and Python str.isspace() characters are forbidden. Absent rollback or transfer is represented by null, never an omitted key. · čeština
Records sort by ASCII stable_id then numeric version. Versions run from 1 to the pinned META upper version without gaps or duplicates. Repeated URLs are not deduplicated; state, fallback and transfer versions need not represent a URL change. Unknown extra stored attributes are ignored. · čeština
A missing or invalid version is replaced by a marker such as {"stable_id":"2222222222","version":2,"error":"malformed_record"}. It exposes no value from the invalid record and means the history is incomplete. Both the record count and checksum include markers. An empty account contains only the declaration and final LF, with records=0. · čeština
Example
{"format":"durableqr-history-file","format_version":1}
{"stable_id":"2222222222","version":1,"url":"https://example.org/old","actor":"11111111-1111-1111-1111-111111111111","timestamp":"2026-11-02T12:00:00.000Z","rolled_back_from":null,"transferred_from":null,"source":null}
{"stable_id":"2222222222","version":2,"url":"https://example.org/new","actor":"11111111-1111-1111-1111-111111111111","timestamp":"2026-11-02T12:01:00.000Z","rolled_back_from":null,"transferred_from":null,"source":null}
{"stable_id":"2222222222","version":3,"url":"https://example.org/old","actor":"11111111-1111-1111-1111-111111111111","timestamp":"2026-11-02T12:02:00.000Z","rolled_back_from":1,"transferred_from":null,"source":null}
Ownership and consistency
The export covers codes of the current owner in all six states, including frozen and deleted. Deleted-code tombstones retain historical URLs in this private file. A transfer recipient sees history from before the transfer, including pseudonymous actors; the previous owner loses access once META changes, even if the index is delayed. A downloaded copy cannot be recalled. · čeština
GSI1 is eventually consistent: new codes and accepted transfers may be absent until a later export. Neither count nor digest proves completeness. Strongly consistent META is checked before and after version reads; ownership or version changes during collection return 503 for the whole file. There is no atomic multi-code snapshot or transfer lock, and changes after the final read remain possible. Export again later if necessary. · čeština
Limits and failures
The synchronous export allows at most 50 GSI1 keys and 100 versions in total, 1 MiB UTF-8 file bytes and 4 MiB serialized Lambda proxy envelope. A 413 is not a first page and cannot be continued; repeated rapid retries do not reduce the history. Throttles are best-effort global per route, not per account: panel 0.0033/s and integrator 0.0008/s, burst 1, independent of map export. · čeština
| Status | Meaning |
|---|---|
| 400 | Unsupported query or missing integrator User-Agent |
| 401 | Missing or invalid JWT identity |
| 403 | API-key or api_access denial |
| 413 | Key, version or size limit exceeded; no file |
| 429 | Gateway or DynamoDB throttle |
| 503 | Deadline, SDK failure, invalid index or META, or changed META |
Application refusals use standard JSON message and Cache-Control: no-store; application 429 and 503 include Retry-After. Gateway errors follow the gateway contract and do not promise application headers. Refusals contain no file fragments, checksum or count headers. There is no public storage fallback. · čeština