Introduction
Quantum Elixir's developer platform exposes seven independent REST APIs. They share a single design language so once you've integrated one, the others feel familiar:
- Bearer-token auth with scoped API keys.
- JSON request and response bodies, predictable envelope shape (
{ data: ... }on success,{ error: ... }on failure). - Cursor or offset pagination on every list endpoint.
- HMAC-SHA256-signed webhooks for asynchronous events.
- OpenAPI 3.1 specs per product, downloadable from the API reference.
Core principles
One sign-in, scoped keys. A single org owns all seven products it has purchased. API keys can be scoped narrowly — a backend service that only needs to evaluate fraud risk gets evaluate:write, nothing else.
Async by default for heavy work. PDF parsing, document extraction, screening — these enqueue jobs and return immediately with an ID. Subscribe to webhooks or poll for the result. The synchronous fast-path endpoints (e.g. transaction evaluation) are documented per-product.
Idempotency you control. Pass your own externalId on writes; we de-duplicate. Retries are safe on transient errors.
Indonesian first, but not Indonesia-only. All amounts default to IDR but every product accepts ISO-4217 currencies. KTP is the only document type Identity Platform supports today — by design (see the Identity overview).
Production access is gated
Sandbox keys are self-serve. Production keys require a signed Master Service Agreement and (for AML, Identity, and Anti-Fraud) a regulatory review. Contact sales@quantumelixir.tech to start.
What you'll need
- A sandbox account — sign up at the dashboard for whichever product you're integrating. Each product has its own dashboard URL; one Quantum Elixir login authenticates you across all of them.
- A sandbox API key with the scopes you need. Issue keys from your dashboard's Settings → API Keys page.
- A webhook receiver if you'll consume async events (recommended for everything except the simplest read-only integrations).