Authorizations
The OneBalance API uses API keys to authenticate requests. All API requests require authentication using an API key passed in the x-api-key
header:
curl -X 'GET' \
'https://be.onebalance.io/api/path-to/endpoint' \
-H 'x-api-key: ${ONEBALANCE_API_KEY}' \
...
A public API key is available for testing purposes with limited usage: 42bb629272001ee1163ca0dbbbc07bcbb0ef57a57baf16c4b1d4672db4562c11
.
All API requests must be made over HTTPS. Calls made over plain HTTP will fail. API requests without authentication will also fail.
Learn how to generate API access tokens at OneBalance Docs.
Body
Quote request with support for multiple account types (v3)
Source configuration for the quote
Destination configuration for the quote
Slippage tolerance in basis points (1/100th of a percent). For example, 50 = 0.5%, 100 = 1%, 1000 = 10%.
x >= 1
50
Response
Quote generated successfully
Quote response with support for multiple blockchain types (v3)
Unique quote identifier
"0xcd3a5cfe80d1b84db755bfb8ebe0a617ff153cc48ab6d5ab28436386f06ce100"
Array of accounts used in this quote
1
- Role-based Account
- Basic Account
- EIP-7702 Account
- Solana Account
[
{
"type": "solana",
"accountAddress": "J5CCzBULFax899tcirb6wMbenQUd8whbaetG7EfSick5"
}
]
Array of blockchain operations to execute, supporting both EVM and Solana
- Option 1
- Option 2
Unix timestamp when the quote expires
"1752673847"
Cryptographic signature to verify quote integrity
"0x1ae7e61279f297d5e6bd702388db0069a3cc2b5168eecd91b53ea0b8bbdf7c412742dd8f0ab778c9a3faa7be38031ce6279b65c202b920c65632840accf01d021c"
Slippage information for origin and destination
Fee breakdown by asset type