Documentation Index
Fetch the complete documentation index at: https://docs.yativo.com/llms.txt
Use this file to discover all available pages before exploring further.
Overview
Test crypto transactions in the sandbox — send testnet tokens, estimate gas fees, and query transaction history, all without spending real funds. Sandbox base URL:https://crypto-sandbox.yativo.com/api/v1/
Get a Gas Fee Estimate
Estimate the gas fee for a transaction before sending.Blockchain to estimate gas for:
ethereum, solana, bitcoin, polygon, bsc, base, xdc.Transaction speed:
low, medium, high. Defaults to low.Optional USD amount, for calculating gas as a percentage.
Response
Send a Transaction
Send testnet tokens from your sandbox wallet to another address.The ObjectId of the account that owns the source asset.
The ObjectId of the asset (wallet) to send from.
Destination blockchain address. Must be a valid testnet address for the specified chain.
Amount to send in the token’s native units, e.g.
25.Blockchain network:
solana, ethereum, base, etc.Token ticker / short name:
"USDC", "ETH", "SOL", etc. Must match the asset record.Transaction category:
"personal", "business", "payment", "other", etc.Transaction speed:
"low", "medium", "high". Defaults to "medium".Optional human-readable note.
Pay gas from the wallet’s own native balance. Defaults to
false.Response — Transaction Submitted
List Transactions
Retrieve a paginated list of all transactions for your sandbox account.Page number. Defaults to
1.Transactions per page. Defaults to
20, max 100.Filter by status:
pending, confirmed, failed, cancelled.Filter by blockchain:
solana, ethereum, etc.Response
Transaction Status Values
| Status | Description |
|---|---|
pending | Submitted to the blockchain, awaiting confirmation. |
confirmed | Confirmed on-chain. |
failed | Transaction failed (insufficient gas, invalid address, etc.). |
cancelled | Cancelled before broadcast. |
Testing Tips
Test insufficient balance errors
Test insufficient balance errors
Attempt to send more than your wallet balance. Your application should handle this gracefully.
Test idempotency
Test idempotency
Send two transactions with the same
idempotency_key. The second call should return the original transaction rather than creating a duplicate.Poll for confirmation
Poll for confirmation
After submitting a transaction, poll
POST /transactions/get-transactions filtering by the transaction_id until the status changes from pending to confirmed or failed.
