Skip to main contentSubscribe to API updates via RSS at https://docs.onebalance.io/changelog/api/rss.xml.
Improvements
- Add complete list of all fail reason codes with detailed descriptions and categories (General Failure Reasons, Execution Revert Specific Reasons, Jupiter Specific Failures)
- Add documentation link to https://docs.onebalance.io/api-reference/error-codes for detailed explanations and troubleshooting steps
- Add “CALL” enum value to action.yaml and action-v3.yaml for contract call operations
- Enhance API documentation with better categorization and explanations for developers
New Features
Fail Reason Field:New Features
Slippage Tolerance Configuration:Improvements
- Create shared slippage tolerance model to avoid code duplication across API versions
- Remove deprecated
transfer-quote and swap-quote endpoints and their associated models
- Fix status schema validation in transaction history examples
- Correct nested status structure to flat format across all history responses
- Add missing chain properties to chain operations in examples
Improvements
- Added
symbol, name, and decimals fields to the destination-asset-used model to match actual API responses. These optional fields provide token metadata when available.
Improvements
- Fix status field structure: changed from object wrapper to direct string enum
- Add missing
chain field to v1 operation-details model
- Add missing
chainId field to v3 operation-details model for backwards compatibility
- Fix all response examples that incorrectly showed
status.status instead of direct status string
- Add multi-input response example showing cross-chain aggregation from multiple source chains
Improvements
Enhanced documentation for chain-specific token spending capability and V3 prepare-call-quote endpointChain-Specific Token Spending:
- Added explicit mentions of chain-specific asset spending in quote endpoint descriptions
- Enhanced asset field descriptions with clear choice explanations between aggregated and chain-specific assets
- Added “Asset Flexibility” section to V1 quote endpoint highlighting both aggregated and specific asset options
- Enhanced V3 quote endpoint with prominent “Chain-specific token spending” capability callout
- Improved asset field descriptions across quote models with concrete CAIP-19 examples
- Better documentation of when to use aggregated vs chain-specific assets for optimal user guidance
V3 Prepare-Call-Quote Documentation:
- Created separate V3 prepare-call-quote endpoint documentation at
/v3/quote/prepare-call-quote
- Added multi-account support with mixed Solana and EVM accounts
- Documented cross-chain contract call capabilities with source asset bridging
- Added examples for Solana USDC/SOL to EVM contract execution
- Included EIP-7702 delegation support documentation
- Created V3-specific request and response models with multi-account schemas
V3 Call-Quote Documentation:New Features
Add aggregatedAssetId filtering to v3 aggregated balance endpoint and clarify token amount formattingBreaking change for v3 aggregated balance endpoint:
- Add
aggregatedAssetId parameter to /api/v3/balances/aggregated-balance endpoint for filtering specific aggregated assets
- Parameter supports comma-separated list of aggregated asset IDs (e.g., “ob:eth,ob:usdc,ob:arb”)
- When provided, response only includes the specified aggregated assets instead of all available assets
- Validation requirement: At least one of
assetId or aggregatedAssetId must be provided and non-empty
- Add 400 Bad Request response for validation errors when neither parameter is provided
- Add missing
accounts field to response schema containing parsed EVM and Solana addresses
- Update all response examples to match actual API behavior with correct asset ID prefixes and response structure
- Add realistic examples based on actual API responses for both filtered and specific asset queries
Token amount documentation improvements:
- Update token amount field descriptions in schemas to specify that amounts should be provided in the smallest unit considering token decimals
- For example, if a token has 6 decimals, “1” token should be represented as “1000000”
New Features
Add EIP-7702 support and improve multi-chain patterns for OpenAPI specificationEIP-7702 Features:Multi-chain Improvements:
- Update hash patterns to support both EVM (0x format) and Solana (base58) transaction hashes
- Update user address patterns to support both EVM and Solana address formats
- Add callType enum and sourceAssetBalances to prepare-call-quote responses
- Make factory/factoryData optional in UserOperation schema for deployed accounts
- Remove staging server references from v3 endpoints (Solana support now in production)
Schema Fixes:
- Fix schema validation warnings for fiatValue, recipientAccount, and account type properties
- Improve pattern validation for cross-chain operation examples
Solana Support (Beta)
New Features
Multi-Blockchain Support
- Added Solana blockchain support alongside existing EVM chains
- Cross-chain operations between Solana and EVM networks (e.g., SOL → USDC on Arbitrum)
- CAIP standards compliance using CAIP-2 chain identifiers and CAIP-10 account identifiers
New v3 API Endpoints
POST /v3/quote - Generate quotes with multi-account support (EVM + Solana)POST /v3/quote/execute - Execute quotes across multiple blockchain typesGET /v3/status/get-execution-status - Get execution status with cross-chain transaction detailsGET /v3/status/get-tx-history - Retrieve transaction history supporting both EVM and Solana addressesGET /v3/balances/aggregated-balance - Get aggregated balances across multiple accounts and chains
Enhanced Capabilities
- Multi-account architecture - Single API calls can handle both EVM and Solana accounts
- Cross-chain asset aggregation - Unified view of assets like USDC across EVM and Solana
- Solana transaction support - Native SOL and SPL token operations with proper Base58 signatures
- Enhanced examples - Complete documentation with EVM-only, Solana-only, and cross-chain scenarios
Technical Improvements
- CAIP-2 chain identifiers (e.g.,
eip155:1, solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp)
- CAIP-10 account identifiers for recipient addressing
- Updated OpenAPI schemas with new v3 models supporting multi-blockchain operations
- Backward compatibility - All existing v1/v2 endpoints remain unchanged
Supported Operations
- Solana native swaps - SOL ↔ USDC on Solana mainnet
- Cross-chain swaps - SOL → USDC on EVM chains (Arbitrum, etc.)
- Multi-chain balance queries - Single request for balances across EVM and Solana accounts
- Transaction tracking - Unified history view for cross-chain operations
