Request parameters.
Build the unsigned claim calldata for one of four claim types — see DefiClaimType for which companion fields each type requires and which protocol constraints apply (e.g. REWARD_PROTOCOL is not supported for LP protocols; PancakeSwap V3 farming uses LP_FEE, not REWARD_INVESTMENT). Returns an ordered dataList (typically [CLAIM]).
binanceChainId resolution rules*:
Normally resolved from investmentId; the call always executes on that chain.
For claim types other than REWARD_PROTOCOL, any client-supplied binanceChainId is
silently ignored* — passing a different chainId will not redirect the claim.
Exception: REWARD_PROTOCOL with no investmentId — the client MUST pass
binanceChainId (it is the only chain signal).
tokenAddressList optionally narrows the claim scope. Set simulate=true to also receive preview.
Request parameters.
Build the unsigned transaction calldata for a DeFi deposit / stake. Returns an ordered dataList (typically [APPROVE, DEPOSIT], or [DEPOSIT] when the allowance is already sufficient) for the caller to sign and broadcast.
The caller does NOT pass binanceChainId — the service resolves it from investmentId. Set simulate=true to also receive a preview (projected balance change, estimated gas, and lending health-factor change) without broadcasting.
Request parameters.
Build the unsigned transaction calldata for a DeFi redeem / withdraw. Returns an ordered dataList (typically [REDEEM] or [APPROVE, REDEEM]).
Redeem amount is decided by exactly one of ratio or token* (mutually exclusive): - ratio omitted / blank → exact-amount redeem: the amount comes from
token (tokenAddress + amount); the position is not queried. token is required
in this mode (omitting token, or leaving amount blank, is rejected with 40001,
Parameter error; both ratio and token absent is also rejected with 40001).
ratio present → proportional redeem: must parse as a decimal in (0, 1]. The
service queries the user's on-chain position under investmentId and scales each
token's amount by ratio (floored to the token's decimals). ratio="1" is a full (max)
redeem. In this mode token is ignored — the output tokens and amounts are derived
from the position.slippageBps is the slippage tolerance in basis points (e.g. 300 = 3%). The caller does NOT pass binanceChainId — resolved from investmentId. Set simulate=true to also receive preview.
The response also carries redeemDelayDays — the redeem waiting period as a [min, max] day pair (e.g. ["7","10"] = 7–10 days, [] = instant). The wait starts after the redeem tx is confirmed on-chain. See the redeemDelayDays field on DefiTxResponse.
Request parameters.
Build the unsigned transaction calldata for adding liquidity. tokenList supports multiple tokens. Returns an ordered dataList (typically [APPROVE, LP_ADD]).
*Tick range source (provide exactly one group)**:
nftId — append to an existing LP position (reuses its range).priceRange — percentage band (e.g. "5" = ±5%) for a new position.tickLower + tickUpper — explicit raw int24 pair for a new position.
Rules*:If more than one group is supplied, only the highest-priority one above is used and the
others are silently ignored (priority: nftId > priceRange > explicit tick pair).
If none is supplied, the request is rejected (40453).
tickLower / tickUpper are raw int24 values and MUST be aligned to the pool's
tickSpacing, otherwise the request is rejected (40453).
The caller does NOT pass binanceChainId — resolved from investmentId.
Request parameters.
Build the unsigned transaction calldata for removing liquidity. Removal is by nftId + ratio (range (0, 1]) — no tokenList is needed; the per-token amounts are derived from the on-chain position. Returns an ordered dataList (typically [LP_REMOVE]).
slippageBps is the LP-leg slippage tolerance in basis points. The caller does NOT pass binanceChainId — resolved from investmentId.
Request parameters.
Solana-only counterpart to /swap. Shares the full quote → route → vendor buildSwapTx → priceImpact → minReceive → instruction-assembly pipeline; the only difference is the response: instead of returning a signed-and-serialized base64 transaction, this endpoint returns the uncompiled instruction list plus the address-lookup-table (ALT) address list, leaving v0-transaction compilation, signing, and submission to the caller.
Use this when the caller needs to:
prepend / append their own instructions (e.g. fee splitting, custom logging) before signing;
reuse the platform-curated route, slippage, PS-variant rewriting, ALT injection, ComputeBudget overwrite, and ATA batching while still controlling the final wire format.
Only supports binanceChainId=CT_501 (Solana). Other chains return CHAIN_NOT_SUPPORTED (40411). Parameters mirror the Solana subset of /swap (no EVM-only approveTransaction / approveAmount / gasLimit). Supports the custom-fee (Add Fee / referral fee) parameters (feePercent + fromTokenReferrerWalletAddress / toTokenReferrerWalletAddress), with the same semantics as /swap — the fee instructions are injected into the returned uncompiled instruction list.
Request parameters.
Build the on-chain swap calldata for a previously quoted route. The request is matched against the cached quote by quoteId (TTL ~30s); if the entry has expired, QUOTE_EXPIRED (40401) is returned, and if the request parameters disagree with the cached quote, SWAP_QUOTE_MISMATCH (40462) is returned.
Request parameters.
Given a single input token, calculate the paired token amount needed for an LP add. This is a pure computation endpoint — it does not touch the chain and does not deduct any fee. Use it before /transaction/lp-add to size the paired token when only one side is supplied.
Tick range source rules are the same as /lp-add — provide exactly one group: nftId (existing position), priceRange, or tickLower+tickUpper.
If more than one group is supplied, only the highest-priority one is used and the others
are silently ignored (priority: nftId > priceRange > explicit tick pair).
If none is supplied, the request is rejected.
The caller does NOT pass binanceChainId — resolved from investmentId.
Request parameters.
Return the latest realized PnL detail for a specific token held by an address, including buy/sell stats, current balance, and holding duration.
Request parameters.
Return trading performance overview for an address within the selected time frame, including realized PnL, daily PnL breakdown, win rate, and top 3 profitable tokens.
Request parameters.
Return recent realized PnL list for an address.
Request parameters.
Query multiple DEX vendors in parallel and return the priced routes sorted by toTokenAmount (descending). Each route carries an independent quoteId (TTL ~30s) that the swap endpoint consumes to construct calldata for the chosen route.
Request parameters.
Return blockchain networks supported by the DEX aggregator. The supported list is dynamically configured server-side and may change over time.
Pass binanceChainId to filter to a single chain; omit it to get the full list.
Request parameters.
Return all token balances held by an address on a single chain, with pagination support. Set excludeRiskToken=true to filter out airdrop-risk and honeypot tokens (honeypot detection currently applies only to ETH / BSC / SOL / BASE).
Request parameters.
Legacy V1 compatibility endpoint. New integrations should use V2. V1 returns x402Version=1, method-specific facilitatorAddress, and V1 signer-map semantics.
Request parameters.
Return the live x402 V2 payment kinds available to the authenticated Developer Portal project. Use the result to construct HTTP 402 payment requirements. Copy the selected extra object verbatim and refresh cached configuration periodically.
Request parameters.
Look up broadcast orders previously submitted via /pre-transaction/broadcast-transaction. Filter by txStatus or orderId, paginate with cursor.
Request parameters.
Return candlestick (K-line) data for a token.
Request parameters.
Query DeFi positions for one or more wallet addresses across the supported EVM chains. Returns protocol-level position summaries with token breakdowns. Optionally filter by specific chains via binanceChainIds; when omitted, positions across all supported chains are returned.
Position coverage is wider than the protocol list used by data queries and transaction building — see Supported Chains & Protocols for the difference.
Request parameters.
Return swap trade history for a specific address. Supports filtering by time range, token, and trade type.
Request parameters.
Build the on-chain transaction data needed to approve the DEX router to spend a user's ERC-20 token before a swap. Calldata is encoded per the ERC-20 ABI standard (approve() selector + spender + amount).
Request parameters.
Estimate the gas limit (or compute-unit ceiling on Solana) for an unsigned transaction.
Provide either evmTx for EVM chains, solTx for Solana, or tronTx for Tron ("CT_195"), matching the value of binanceChainId.
On Tron the response carries energy/bandwidth fields instead of a single gas limit; gasLimit is the fee limit (in sun) and the energy/bandwidth fields describe resource consumption and pricing.
Request parameters.
Query the current network gas price for the specified chain. The response shape varies by chain family:
evmLegacyGasPrice (legacy gasPrice) and
eip1559GasPrice (baseFee + priority/max fees) when EIP-1559 is supported.solanaGasPrice (compute-unit prices and Jito tips). - Tron ("CT_195") returns an empty data object because Tron has no
on-chain gas-price concept; use the gas-limit endpoint instead.Fields not applicable to the chain family are returned as null.
Request parameters.
Return the holders ranking list for a token, including holding amount, holding percentage, native-token balance, average buy/sell price, realized PnL, and funding source. Up to 100 records. Pagination is not supported.
Request parameters.
Get hot token ranking list. Supports sorting by volume, price change, market cap, etc., with filters for holding distribution, developer behavior, liquidity, and more.
Request parameters.
Get detailed information for a specific DeFi investment product, including APY, TVL, supported tokens (asset / reward / LP / borrow), pool address, fee rate, and investability.
Request parameters.
Return the latest block height that the Binance Web3 node has synced to for the specified chain. Callers can use this to monitor node sync progress for risk control and detect when the node lags behind the canonical chain head.
Request parameters.
Return a leaderboard of top-performing wallets, with sorting and filtering by PnL, win rate, transaction count, and volume.
Request parameters.
Return the list of blockchains supported by address portfolio analysis.
Request parameters.
Get detailed information for a specific DeFi protocol, including description, highlights, CertiK security scores, team, fundraising, social links, and FAQ.
Request parameters.
Query the settlement status of an RFQ order by its platform orderId (returned by POST /order/submit). Poll this endpoint until status reaches a terminal state: FILLED (settled on-chain) or FAILED (settlement failed).
Request parameters.
Return the list of supported RWA token issuance platforms and their basic info.
Request parameters.
Get the list of RWA tokens with underlying asset info. Supports filtering by platform and sector tab.
Request parameters.
Batch query RWA token prices, including on-chain price and underlying reference price.
Request parameters.
Get the underlying company information for an RWA token.
Request parameters.
Get market data for the underlying asset of an RWA token.
Request parameters.
Return the list of blockchains supported by the market service.
Request parameters.
Return comprehensive metrics for a token, including creator and launch info, holding percentages by address type (smart money, KOL, sniper, bundler, fresh wallet, etc.), and token tags.
Request parameters.
Return token balances for a specific list of (chain, contract) pairs. Up to 20 entries per request. Set excludeRiskToken="0" to exclude risk-flagged tokens (default), or "1" to include them.
Request parameters.
Return basic metadata for a token: name, symbol, logo, decimals, creator address, creation time, and tag info.
Request parameters.
Return developer profile for a token, including historical token launch stats, current holding percentage, and initial funding source.
Request parameters.
Get the latest price for tokens. Supports batch queries, up to 100 tokens per request.
Request parameters.
Return on-chain trade history for a token. Supports tag filtering and wallet address filtering.
Request parameters.
Get token price and trading data (volume, transactions, market cap, holders, etc.). Supports batch queries for up to 100 tokens.
Request parameters.
Return the top liquidity pools for a token, including pool name, protocol, liquidity in USD, pool address, and per-token composition.
Request parameters.
Return the top profit-making addresses for a token, ranked by realized PnL descending. Includes holding amount, average buy/sell price, realized PnL, and funding source. Up to 100 records. Pagination is not supported.
Request parameters.
Return the latest swap trades from tracked addresses (smart money, KOL, or custom address list).
Request parameters.
Look up the full on-chain transaction detail by binanceChainId + txHash. Returns one or more entries describing transaction inputs, outputs, internal calls, and token transfers.
Request parameters.
Return on-chain transaction history for a wallet address across one or more chains. Results are limited to the most recent 6 months and sorted by time (descending). Supports cursor pagination, time-range filtering, and token-contract filtering.
Request parameters.
Look up the on-chain status of a DEX swap by binanceChainId + txHash.
Response semantics:
Transaction not found: data is null (not HTTP 404).
Transaction failed: status=failed with errorMsg; aggregator
business fields (txType, dexRouter, fromTokenDetails,
toTokenDetails) are null.
Transaction succeeded: status=success with full token details
when an aggregator event is present.
Request parameters.
Return the blockchain networks supported by the Transaction service for gas estimation, simulation, and broadcasting. The list is dynamically configured server-side and may change over time.
Request parameters.
Return blockchain networks for which the Wallet service can return balances. The supported list is dynamically configured server-side and may change over time. Pass binanceChainId to filter to a single chain; omit to get the full list.
Request parameters.
Get a WebSocket auth token before connecting to the WebSocket stream service. For details on WebSocket usage, please refer to the WebSocket documentation.
Request parameters.
List available DeFi investment products. Filter by protocol, chain, investment type, or contract address. Results are paginated and sortable.
Request parameters.
List supported DeFi protocols with optional filtering by chain and investment type. Results are paginated and sortable.
Request parameters.
Combines quoting and swap-transaction construction into a single call. Unlike the two-step /quote + /swap flow, this endpoint does not require a prior /quote call or a quoteId — it returns the executable calldata / swapTransaction directly, eliminating one HTTP round-trip.
Use this endpoint for latency-sensitive trading when the vendor is known upfront. The response shape is identical to /swap, so clients can reuse the same response parsing logic for both endpoints.
Request parameters.
Search RWA tokens by keyword or contract address.
Request parameters.
Search tokens by symbol or contract address.
Request parameters.
Generic function to send a request.
The API endpoint to call.
HTTP method to use (GET, POST, DELETE, etc.).
Query parameters for the request.
Body parameters for the request.
A promise resolving to the response data object.
Generic function to send a signed request.
The API endpoint to call.
HTTP method to use (GET, POST, DELETE, etc.).
Query parameters for the request.
Body parameters for the request.
A promise resolving to the response data object.
Legacy V1 on-chain settlement endpoint. New integrations should use V2. This operation can move real funds and is irreversible. V1 additionally returns confirmations in the settlement result.
Request parameters.
Submit a verified x402 V2 authorization on-chain. This operation can move real funds and is irreversible. For permit2-upto, provide settleAmount in atomic units. Business failure is returned as HTTP 200 with data.success=false; reconcile any non-empty transaction hash before retrying.
Request parameters.
Simulate transaction execution off-chain to predict its outcome before broadcasting. The response includes the predicted execution status, balance changes per affected account/token, and ERC-20 allowance changes (EVM chains).
Provide either evmTx (EVM chains), solTx (Solana), or tronTx (Tron "CT_195") matching binanceChainId. On Tron, allowanceChanges is returned as an empty array.
Note: Metis (chainId 1088) is not supported by this endpoint.
Request parameters.
Submit a signed RFQ order to the backend for on-chain settlement via the corresponding vendor relayer. Only used when executionMode=RFQ (equity / RWA tokens such as Ondo and BStock).
Flow*: GET /quote → pick an RFQ route → GET /swap → sign rfq.typedDataToSign with EIP-712 (eth_signTypedData_v4) → call this endpoint → poll GET /order/{orderId} until FILLED or FAILED.
Idempotency*: Submitting with the same requestId within 30 minutes returns the original result without re-calling the vendor. Use a new UUID for each distinct order; reuse the same UUID when retrying.
Request parameters.
Legacy V1 off-chain verification endpoint. New integrations should use V2. Portal identity is resolved from the API Key project, so merchantId is omitted from the external request.
Request parameters.
Validate an x402 V2 payment authorization off-chain without spending funds or broadcasting a transaction. Portal identity is resolved from the authenticated API Key project; omit merchantId. A validation failure is returned as HTTP 200 with data.isValid=false.
Request parameters.
Broadcast a client-signed transaction to the chain via the Binance Web3 API relay. Returns the transaction hash and an internal
orderIdyou can use to track on-chain status via the post-transaction service. Optional MEV protection (EVM chains only) routes the transaction through a private mempool to mitigate front-running and sandwich attacks. Tron and Solana do not support MEV protection; the flag is ignored on these chains.