Documentation
REST API for the Abundera QR Pro dynamic-QR platform. Create codes, retarget destinations, pull scan analytics, manage teams, and ship webhooks.
API specification
The Abundera QR Pro API follows OpenAPI 3.1. Browse the interactive reference, download the spec, or import it into your preferred API client.
Authentication
The QR Pro API uses bearer-token authentication:
- API keys · product-scoped, prefix
abnd_qrpro_, managed at abundera.ai/account/api-keys. Available on Business, Team, and Agency plans (Solo is dashboard-only). - The raw
abnd_qrpro_…token is shown exactly once at creation, store it immediately. We persist only its SHA-256 hash; lost keys cannot be recovered.
Authorization: Bearer abnd_qrpro_…
Base URL and format
Base URL: https://pro.qr.abundera.ai/api
Request format: JSON (Content-Type: application/json) on POST / PATCH / DELETE.
Response format: JSON (application/json; charset=utf-8).
Rate limits: per API key, surfaced via X-RateLimit-Limit / -Remaining / -Reset response headers. 1k/10k/50k requests per UTC day on Business / Team / Agency. The redirect hot path (aqr.net/{shortcode}) is unauth and has no per-scan budget.
Quick example
curl -X POST https://pro.qr.abundera.ai/api/v1/codes \
-H "Authorization: Bearer abnd_qrpro_…" \
-H "Content-Type: application/json" \
-d '{"name":"Spring menu","destination":"https://example.com/menu","payload_type":"url"}'Discovery (well-known)
Auto-discovery endpoints under /.well-known/ (RFC 8615):