Triple-A Developer DocsTriple-A Developer Docs
Triple-A dashboard

Environments

View as MarkdownView this page as plain textOpen in ChatGPTAsk questions about this pageOpen in ClaudeAsk questions about this pageOpen in PerplexityAsk questions about this page
Connect to CursorUse these docs in CursorConnect to VS CodeUse these docs in VS Code

Each Triple-A API has one production base URL, and every request path in the API reference is relative to it. Stablecoin sandbox requests use the same host as live requests, so what separates the two environments is the credentials and flags you send. This page lists the base URLs and explains how to choose an environment.

Base URLs

The table below lists the production base URL of each API. Stablecoin Payments and Stablecoin Payouts share one host and one path prefix.

APIBase URL
Stablecoin Paymentshttps://api.triple-a.io/api/v2
Stablecoin Payoutshttps://api.triple-a.io/api/v2
Local Currency Payoutshttps://api.triple-a.io/api/fiat-payout/v1
KYChttps://api.triple-a.io/kyc-api/v1

Sandbox and live

Stablecoin sandbox mode doesn’t have its own URL. The following table shows how you mark a request as a test request for each endpoint. For the full setup, see Sandbox and test mode.

EndpointHow to select the environment
Make a payment requestAdd "sandbox": true to the request body.
Make a payment request (specific account)Pass your Sandbox API ID for a test payment, or your Live API ID for a live one.

Local Currency Payouts and KYC don’t document a sandbox mode. Ask your Triple-A account manager how to test these APIs before you go live.

Credentials

Your access token comes from the same endpoint in every environment, and you send it as a bearer token. The Sandbox API ID and the Live API ID are separate values in the Triple-A dashboard. See Authentication and Get your API credentials.

Next steps

These pages are the best places to go next.