API Changelog

​

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

• Add optional failReason field to execution status responses when status is REFUNDED
• Add fail-reason enum schema with 12 standardized refund reasons (SLIPPAGE, INSUFFICIENT_BALANCE, TIMEOUT, etc.)
• Updated both v1 and v3 status endpoints (/status/get-execution-status and /v3/status/get-execution-status)
• Updated transaction history endpoints (/status/get-tx-history and /v3/status/get-tx-history) to include failReason in historical records
• Added response examples showing refunded transactions with detailed fail reasons
• Backward compatible: field only appears when status is REFUNDED
• Enhanced error handling documentation with quote execution failure guidance
• See Refund Reasons Guide for detailed explanations and handling strategies

​

New Features

• Add optional slippageTolerance parameter to all quote request models (V1, V2, V3)
• Parameter accepts positive integer values in basis points (e.g., 50 = 0.5%, 100 = 1%, 1000 = 10%)
• Helps reduce quote refunds and improve user experience by allowing configurable slippage tolerance
• Available on quote endpoints, call-quote endpoints, and prepare-call-quote endpoints
• Also supported on V3 endpoints: /v3/quote, /v3/quote/call-quote, and /v3/quote/prepare-call-quote
• Backward compatible - parameter is optional to maintain existing integrations
• See Slippage Tolerance Guide for detailed configuration and best practices

​

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

• Updated account models

​

Improvements

• 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

• 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

• Created separate V3 call-quote endpoint documentation at /v3/quote/call-quote
• Added multi-account call execution with cross-chain support
• Documented complex DeFi interactions using multiple account types
• Included EIP-7702 delegation workflow examples
• Created call-request-v3.yaml model for multi-account call requests
• Enhanced error handling for multi-account configuration validation

​

New Features

• 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

• 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 delegation and delegation-signature models for EIP-7702 authorization flow
• Enhance account models with deploymentType field to distinguish ERC4337 vs EIP7702 accounts
• Update chain-operation model with optional delegation field for execution
• Add EIP-7702 examples to prepare-call-quote and call-quote endpoints showing delegation workflow
• Include cross-references to EIP-7702 integration guides for detailed implementation steps

• 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)

• Fix schema validation warnings for fiatValue, recipientAccount, and account type properties
• Improve pattern validation for cross-chain operation examples

​

Improvements

• Replace ds: prefix with ob: for aggregated asset list

​

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 types
• GET /v3/status/get-execution-status - Get execution status with cross-chain transaction details
• GET /v3/status/get-tx-history - Retrieve transaction history supporting both EVM and Solana addresses
• GET /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

​

Improvements

• Add new EXECUTED state to execution status endpoint