DevelopersOsai website ↗
API v1
Get started

Rate limits

Use response headers, bounded concurrency and backoff rather than repeated bursts.

Limit scopes

The customer gateway applies institution and credential budgets. Its baseline is 100 requests per minute with a burst allowance of 10 per scope. Plan against the limits configured for your integration; market-data admission has separate feed policies.

Handle HTTP 429

Read Retry-After in seconds. Pause attempts for that scope, add jitter and bound concurrent workers. Do not rotate keys to evade an institution limit. Authentication and permission failures need configuration changes rather than backoff.

Background jobs

  • Checkpoint pagination and command identifiers.
  • Use bounded queues rather than unbounded parallel calls.
  • Use events and targeted reconciliation reads instead of a polling loop for every transaction.
  • Keep original idempotency keys for write retries.

16 suggested pages

Get startedIntroductionIntegrate institutional FX and stablecoin trading with quotes, orders, market data, account records and settlement reporting.Get startedQuickstartMake an authenticated read, request a quote and follow an instruction without losing its original references.Get startedAuthenticationUse the correct authentication scheme for API credentials, Console sessions and market-data feeds.Get startedErrorsDistinguish invalid inputs, denied access, conflicts, rate limits and uncertain outcomes.Get startedRate limitsUse response headers, bounded concurrency and backoff rather than repeated bursts.Get startedAmounts & precisionKeep minor-unit money, fixed-point FX rates and instrument-scaled quantities exact.Get startedPagination & recoveryUse each resource’s pagination model and preserve stable recovery checkpoints.Financial workflowsQuotes & acceptanceRequest explicit FX economics, review conditions and retain accepted terms.Financial workflowsTrade lifecycleTrack funding, execution and settlement as distinct business transitions.Financial workflowsBalances & transactionsRead institutional financial positions and reconcile movements by currency.Financial workflowsBeneficiariesRegister beneficiaries and coordinate their institutional approval lifecycle.Financial workflowsCredential managementCreate, inspect, rotate and revoke application credentials without exposing secrets.Events & reliabilityIdempotencyPrevent duplicate financial effects across retries and uncertain outcomes.Events & reliabilityWebhooks & verificationVerify deliveries, persist original events and make downstream processing idempotent.Events & reliabilityEvent payloadsUnderstand the customer event envelope and business transitions behind subscriptions.Events & reliabilityDelivery retries & replayRepair webhook delivery without creating a second business event.