Developers

Build on the advisor, not just the rails.

Read a customer’s safe-to-spend, propose an action, verify the sealed record of what happened. Consent enforced at every step, three SDKs, one sandbox, numbers that never guess. Your first call runs in under ten minutes.

Get sandbox keysAPI reference
3
SDKs. TypeScript, Kotlin, Swift
~80ms
p50 read latency (sandbox)
100%
of money math tool-computed
30 days
of replayable test history

Three quickstarts

Each one runs end-to-end in the sandbox in under ten minutes.

Integrate as a financial institution

Surface Qoyla inside your banking app: OIDC sign-in, consent scopes, then safe-to-spend on your home screen.

Read the guide

Place a merchant offer

Match an offer to real spending intent, category signals, never raw transactions, and settle commission cleanly.

Read the guide

Verify a sealed record

Fetch any record by reference and verify its signature chain: reason, approval, action, outcome.

See the code

Everything in the docs

API referenceEvery endpoint, generated from the OpenAPI spec, try calls in the playground.OpenAPI 3.1SDK docsInstall, init and first call for TypeScript, Kotlin and Swift.TS · Kotlin · SwiftWebhooksEvent types, signature verification, retries and replay.HMAC-SHA256AuthenticationFI partner OAuth, merchant API keys, and the consent scopes behind every call.OIDC / OAuth 2.1Rate limitsPer-endpoint, per-tier limits and how to handle a 429 gracefully.Sandbox guideTest customers, test transactions, test approvals, nothing real, everything realistic.Code samplesCopy-paste quickstarts for the three most common builds.SDK changelogFeatures, breaking changes and deprecations, per version.Developer statusSandbox and dev-API uptime, separate from the production status page.

Start in the sandbox today

Keys are free, data is synthetic, and the first call takes five minutes.

Get sandbox keysTalk to an engineer