Skip to main content
The Stabyl API lets your team automate the same money movement and trading workflows you already perform inside Stabyl. Use it for backend jobs, internal tools, reconciliation systems, and trading automation that operate on your own Stabyl account.
Create your staging API keys in the Stabyl staging app. Staging keys work only with https://api-staging.stabyl.com/v1. Staging access does not grant production access.
Production API access requires completed KYB and an explicit invitation from Stabyl. The invitation provides the production onboarding instructions. Do not send requests to the production API until your organization has received that invitation and provisioned production credentials.

​
What You Can Automate

Partner withdrawals are authorized by an API key with the wallets:withdraw scope and an Ed25519 request signature. They do not require an emailed verification code or a separate withdrawal token after submission.

​
Base URLs

The production URL is available only to organizations that have completed KYB and been invited by Stabyl.

​
API Conventions

All requests use HTTPS. JSON writes require Content-Type: application/json. Authenticated routes require X-Api-Key. Successful JSON responses use a response envelope:
Errors use the same envelope shape:
One exception: a request that cannot be parsed at all, such as a missing Content-Type: application/json header (415), malformed JSON (400), or an unknown body field (422), is rejected before the envelope is built and returns a plain-text body. Branch on the HTTP status first and only then on error.code. Timestamps are RFC3339 strings in UTC. Monetary amounts are strings to avoid floating point rounding issues. Stablecoins (USDT, USDC) are settlement rails for the USD wallet, not separate wallet currencies.

​
Design Principles

  1. Keep API keys server-side and grant each key only the access it needs.
  2. Discover wallet routes from the API instead of hardcoding chain availability.
  3. Treat order writes as asynchronous; read the order after submission for canonical status.
  4. Send a UUID Idempotency-Key on every create, cancel, and replace order request, and set client_order_id on orders you must be able to find again.
  5. Reuse a withdrawal body idempotency key only for retries of the same request.
  6. Reconcile from transaction and order reads, not from manual exports or UI state.
  7. Remove simulation calls from production code paths.