Quro

Start a QR workspace

Select an accessible canonical Auth workspace. Read categories, statuses and templates, create a series when needed, then create a code using plain, custom or a bound published Brand design. Retain returned ids and slugs; labels do not establish identity or authority.

Review codes before distribution

Compare the saved destination and design, resolve the real redirect and scan the rendered code before printing. A creation response or queued publication event does not prove propagation, reachability or recipient delivery. Changing a destination affects distributed redirect codes. Slugs are set at creation and are not accepted by the update action. Static payloads use generated slugs and standard tier; static and redirect QR types cannot be converted in place.

Generate and reconcile a series

Generation returns counts and a bounded preview. Check partial failures with HTTP 200 and discover the full series inventory through numbered pages. Repeating a request can create suffixed duplicates. Marking a series completed does not disable its codes, and the catalog publishes no series reopening or deletion action.

Inspect activity and health

Distinguish scan counters, daily rollups and operational creation/change events. Unknown destination health is not healthy. refresh_health="true" probes destinations and stores refreshed health; review targets and confirm this operation. Use string false for cached health.

Export and delete deliberately

Workspace exports are stored snapshots of selected non-deleted code fields. Organization export includes broader app, analytics and discovered KV data. Code deletion is soft with an inactive tombstone; exact reads can still return it. Organization erasure checks the included stores but retains backups. Empty-workspace archival delegates its final decision to Auth.

Action guides

• Export organization records: Returns organization-scoped app tables, analytics rows, redirect records and discovered scan namespaces without including credentials.
• Erase organization records: Deletes the authenticated organization’s Quro app and analytics records and corresponding discovered KV records, then checks that the included stores are empty. Backups are retained.
• Get Quro dashboard widget: Returns a workspace-scoped widget contract and aggregate code, series and scan counts for dashboard presentation.
• Archive empty Quro workspace: Checks the verified workspace is empty, asks Auth to archive it, then removes Quro’s identity-only mirror. A successful response is HTTP 204 with no body.
• List QR codes: Lists non-deleted workspace codes with filters, page metadata, tier counts and scan counts; basic codes remain in the same canonical inventory.
• Create QR code: Persists a code, design snapshot and redirect cache entry, records a creation event and queues a local publication notification for an active code.
• Get QR code: Reads one code by exact numeric id or slug within the verified workspace, including its design, scan count and series. Exact reads can return soft-deleted records.
• Update QR code: Updates the selected code and its redirect/design cache. Destination changes affect existing printed codes; slug changes can invalidate printed URLs.
• Delete QR code: Soft-deletes a code, sets status_id to inactive and writes a redirect tombstone. The historical D1 record remains, and repeated deletion can still succeed.
• Get scan analytics: Returns scan counters for the selected code or workspace. These counters are read from the configured scan-count store, separately from daily rollups.
• List QR assets and health: Returns paginated code assets, destination health, lifecycle and activity flags. refresh_health=true probes destinations and stores refreshed health, so that option has side effects despite the current read-only catalog flag.
• List QR operational events: Reads dated workspace operational events, including creation and destination changes; parsed details accompany the retained details_json field.
• List daily scan rollups: Returns dated workspace daily rollups for scans and redirect/refusal categories.
• Get QR analytics summary: Summarizes workspace inventory, activity, failures, campaign aggregates and top assets over the selected date window.
• Get QR reference metadata: Reads the supported categories, statuses or tiers used by code-management forms.
• List QR series: Lists workspace series with code counts, optional template metadata and unassigned-code counts.
• Create QR series: Persists a named series, applying an exact supported template and its dashboard defaults when supplied.
• List series templates: Returns searchable template definitions, categories and supported statuses; selecting one alone creates no series or code.
• Get series dashboard: Reads the series identity and saved dashboard; supported templates can supply a default dashboard when no saved state exists.
• Update series dashboard: Replaces the saved dashboard object or restores supported template defaults; it does not merge a partial dashboard.
• Generate series QR codes: Generates 1–1000 codes using a naming/URL pattern. HTTP 200 can contain partial failures; codes is a preview of at most ten, and error_messages is at most five.
• List series generation patterns: Returns base and template-specific naming and URL patterns for an existing series within its verified tenant.
• Complete QR series: Marks a series completed and queues a local completion notification. A repeated request can return changed=false; existing codes remain active.
• Create workspace QR export: Stores a ready JSON snapshot of non-deleted workspace code fields and queues a local export-ready event.
• Download workspace QR export: Downloads a stored ready export as a raw JSON array, with an attachment filename; it is not a success/data envelope or a full organization backup.

Evidence

Actual exported Quro Worker with local Miniflare D1/KV and every committed app/analytics migration. Auth, service tokens, Nexus, destination probes and platform archival are synthetic responses; outbound fetch is sealed. Notifications remain in the local outbox. No live redirect propagation, QR scan, destination health, provider delivery, archival or production erasure is established.