API reference
APIs
Three OpenAPI 3-described services: Admin (auth, stores, billing, domains), Store (per-pod commerce primitives), and AI (chat, RAG, embeddings, agents). Every endpoint here is generated from the production spec — if the upstream service changes, the reference updates on the next sync.
Make your first call
Every Tanqory API uses an HTTP Bearer token in the Authorization header. Create a key in your dashboard, then run the call below against https://api.tanqory.com.
curl -X GET 'https://api.tanqory.com/api/v1/stores' \
-H "Authorization: Bearer $TANQORY_API_KEY" \
-H "Content-Type: application/json"Base URL resolved from spec.servers[0] at build time.
Get started
- Quickstart →
Make your first authenticated call in five minutes.
- Authentication →
Bearer JWT, OAuth 2.1, MFA, key rotation.
- Pagination →
Cursor pattern across every list endpoint.
- Errors →
Standard error envelope, HTTP status mapping, idempotency.
- Rate limits →
Per-key headers, 429 handling, backoff.
- Webhooks →
Subscription, HMAC-SHA256 signing, retry policy.
- Versioning →
Dated versions and the 12-month deprecation window.
Endpoints
- Admin API →292 endpoints · 30 resources
Auth, stores, billing, domains, notifications, analytics.
- Store API →1336 endpoints · 114 resources
Products, orders, customers, inventory, checkout, content, themes. OpenAPI export is in progress — endpoint count will appear once upstream completes.
- AI API →46 endpoints · 10 resources
Chat, RAG, embeddings, image generation, semantic search, agents.
Build with
Coverage + legal
Resources
- Status ↗
Real-time platform health across Admin, Store, and AI services.
- Trust Center ↗
Security and compliance posture — subprocessors, security.txt, audit reports.
- Subprocessor register ↗
Current list of data sub-recipients with jurisdiction and purpose.
- Support ↗
Direct escalation to the developer-support inbox.