We release the v4 API iteratively, in partnership with the clients building on it. The whole contract is published so you can build against it in the sandbox today. The groups tagged under construction in the sidebar return mocked data only, so you can code to their shape before they go live. What’s available lists each area’s status, and the Crypto as a Service guides walk through every flow. Endpoint definitions can still change before general availability; see the API deprecation policy.
Base URL
Authentication
Every request carries theApi-Access-Key header.
POST, PATCH, and DELETE also carries an Idempotency-Key, and is signed with Api-Signature and Api-Timestamp.
Api-Signature is a hex-encoded Ed25519 signature over timestamp_epoch_seconds + uppercase(http_method) + request_path + request_body, and Api-Timestamp is the same timestamp in Unix epoch seconds. Read Setting up and Signing requests before sending signed requests. Getting started covers idempotency, batch results, and the If-Match concurrency header.
Notifications
Webhooks for the v4 API are coming soon. Until then, poll the read endpoints to follow an object to its final state.Pagination and errors
List endpoints acceptlimit (page size) and after (cursor), and return page.endCursor to continue from. Errors carry a JSON body with a human-readable message. Batch endpoints return a result per item instead, with status: ERROR and an error on the items that failed.
Endpoint areas
Accounts
Create and manage accounts, beneficiaries, fee configurations, and compliance profiles.
Balances and transactions
Read balances and the transaction feed per account.
Deposits
Deposit instructions per asset, and deposit attribution for crypto.
Trusted destinations
Register and look up approved withdrawal destinations.
Orders and withdrawals
Place and track orders, and move funds out.
Policy engine
Register approval keys, write policies, and endorse pending actions.