Postman collection
Try the Stables API without writing code. The Postman collection has every endpoint in the API reference, plus the main integration flows set up as ordered requests that pass IDs from one step to the next.
Download the Postman collectionThe collection is generated from the same OpenAPI spec as the endpoint pages in this reference, so it is updated whenever the API is.
Import it into Postman
- Download the collection above.
- In Postman, select Import and drop in
stables-api.postman_collection.json. - Open the Stables API collection, go to the Variables tab and set
api_keyto your sandbox key (it starts withsti_test_). See Setup a sandbox environment to create one. - Save the collection.
base_url is set to sandbox (https://api.sandbox.stables.money). To call production, change it to https://api.stables.money and use a production key.
To update the collection later, download it again and import it. Postman offers to replace the existing copy; your variable values are replaced too, so note your api_key first.
Key flows
The Key flows folder follows the quickstart. Run each folder's requests from top to bottom. Each step saves the IDs it returns, such as customer_id, quote_id and transfer_id, into collection variables, so the next request works without copying values.
| Flow | What it does |
|---|---|
| 1. Onboard an individual customer | Create a customer with KYC details, then check their entitlements and KYC capabilities |
| 2. Onboard with a hosted verification link | Create a customer and get a hosted link where they complete verification |
| 3. Off-ramp: stablecoin to bank | Validate bank details, quote USDT to USD, create the transfer and simulate the customer's deposit |
| 4. Pay out from your balance | Check your balance, request a deposit wallet, and create a transfer paid from your balance |
| 5. Payment routes | Create a USD virtual account, simulate a deposit and read its transaction history |
| 6. Webhooks | Create a webhook subscription, list deliveries, then delete it |
| 7. Compliance requests (RFIs) | List RFIs, read one and fetch the evidence form for a requirement |
Flows 3, 4 and 5 need a customer approved for the right entitlement, so run flow 1 or 2 first. In sandbox, individual customers are approved automatically when you send one of the Sandbox Test Documents: replace the BASE64_... placeholders in Create Customer with a base64 data URI of a test document and selfie.
The simulate-deposit requests only work in sandbox.
In production, Create Transfer from Balance spends real funds as soon as it is sent.
API reference
The API reference folder has a request for every endpoint, grouped by resource like the sections of this reference. Request bodies are filled in with example values from the spec; edit them before sending. Path parameters use the same collection variables as the flows, so IDs saved by a flow are reused here.
Authentication and idempotency
The collection sends your key in the X-Api-Key header on every request. See Authentication.
Requests that require an Idempotency-Key header send a new UUID each time ({{$guid}}). To retry an operation without repeating it, replace {{$guid}} with a fixed value and send it again. See Idempotency.