Developer Portal

Overview

QAAR is designed as a workflow-driven platform rather than a simple QR redirect system. Integrations can be built around record lookup, scan handling, relay workflows, incident support, exports, and organization-aware operations.

Typical integration use cases include branded deployments, controlled access flows, support and incident dashboards, and interoperability with external systems.

Core Resources

• Records
• Scan events
• Incidents and support workflows
• Relay and notification actions
• Evidence and audit events
• Organization-aware deployments

Illustrative Endpoints

GET /scan/<token>

Resolve a public scan entry point and return the correct public-safe view or workflow handoff.

GET /api/incidents

Retrieve incident or operational queue data for command-center style interfaces.

GET /api/incident/<id>/detail

Retrieve richer detail for a specific incident, including status, context, evidence, and action history.

POST /api/incident/<id>/action

Apply a workflow action such as approve, reject, escalate, close, or reopen based on policy and permissions.

POST /api/incident/<id>/evidence

Attach supporting information, files, notes, or operational evidence to an incident record.

Authentication & Policy

Integrations should assume that public scan access, protected field access, support actions, and organization workflows may all follow different permission and policy rules.

In practice, this means public-safe views, authenticated operator actions, and approval-based access flows should be handled as distinct access layers.

Example Response Shape