QR Hero Help center

API & integrations

API & MCP integrations

Automate QR Hero with the REST API and Model Context Protocol tools.

Related in the dashboard: settings.api-tokens

Developers automate organisations with the same permissions as the dashboard — codes, analytics, domains, wallet reads, and more.

Where to find developer docs

Full reference lives on the developer docs host:

When DOCS_DOMAIN is unset locally, use /developers on the app host instead.

Authentication

  1. Open Settings → API tokens (requires api_access entitlement).
  2. Create a personal access token with the minimal abilities needed.
  3. Send Authorization: Bearer <token> and Accept: application/json on every request.

Tokens are organisation-scoped via Sanctum teams — the active org at creation time applies.

REST vs MCP

Surface Best for
REST /v1 Backend integrations, ETL, mobile apps
MCP tools AI assistants (Cursor, Claude Desktop) with schema-validated calls

Both share rate limits and wallet metering. 429 responses include Retry-After.

Safety model

Sensitive MCP tools use confirm-then-execute — the server returns a confirmation token before mutating data. Automations should persist that token within the TTL window.

Excluded operations

Account profile changes (email, password) and some payment writes remain dashboard-only by design.

Getting help

Use the in-app assistant or these user guides for workflow questions; use developer docs for endpoint schemas and code samples in cURL, JavaScript, Python, PHP, and C#.