Skip to main content

Overview

The Yativo Crypto Sandbox is an isolated testing environment that mirrors the production API. All wallets and transactions in sandbox run on testnets only — no real funds are ever involved.

Sandbox URL

https://crypto-sandbox.yativo.com/api/v1/

Production URL

https://crypto-api.yativo.com/api/v1/

Quick Start — Use the Shared Sandbox Account

To get started immediately without registering, use the shared sandbox API key below. It’s public and pre-populated with accounts, wallets, customers, and a webhook so you can explore every endpoint right away.
This is a shared public account for exploration only. Do not store sensitive data here. For real integration testing, create your own sandbox account with a private API key.

Step 1 — Generate a Bearer Token

For quick documentation testing, use the long-lived docs token (valid 1 year):
This returns a bearer token you can use immediately in the API playground above — no API key or secret needed.
You’ll get back an access_token. The docs token is valid for 1 year; the standard token lasts 60 minutes (call /auth/token again to refresh).

Step 2 — Start calling the API

The shared sandbox account is pre-populated with:
The shared sandbox credentials above can also be used in the API playground on every API reference page in these docs. The docs default to the sandbox base URL — just paste your Bearer token and try any endpoint.

Create Your Own Sandbox Account

For private integration testing with dedicated credentials:
  1. Register at crypto.yativo.com/sign-up
  2. Log in and go to Developer → API Keys
  3. Create an API key — it works against both sandbox and production (just change the base URL)
  4. Use POST /auth/token with your credentials against https://crypto-sandbox.yativo.com/api/v1/

Sandbox vs Production

All crypto wallets created in sandbox are on testnet chains. Addresses generated will never hold real funds. Testnet tokens can be obtained from each chain’s faucet.

Supported Testnet Chains


Sandbox Limitations

  • Yativo Card KYC: Uses a test-mode KYC and card provider. Transactions are simulated.
  • IBAN bank transfers: Cannot receive transfers from real banks — testnet only.
  • Swap rates: Simulated, not live market prices.
  • Email OTPs: Delivered to real email addresses, same as production.
  • Payment Gateway: Use the sandbox simulation endpoint to trigger payment confirmation.
  • Agentic Wallets: Testnet chains only. Use the simulation endpoint to generate mock agent transactions.

Sandbox Simulation Endpoints

These endpoints are only available in the sandbox environment and let you simulate events that normally require on-chain activity:

Environment Variable Pattern

We recommend switching environments with a single variable change:
.env.sandbox
.env.production
Your integration code doesn’t change — only the environment variables.