Get you own node endpoint todayStart for free and get your app to production levels immediately. No credit card required.You can sign up with your GitHub, X, Google, or Microsoft account.
Parameters
sell_token_id— TRC10 token ID being sold, as a numeric string (for example, “1000006”).buy_token_id— TRC10 token ID being purchased, as a numeric string.offset— (optional) starting position for pagination (default: 0)limit— (optional) maximum number of orders to return (default: 20, max: 100)visible— (optional) whentrue, some nodes accept the request more reliably.
Response
orders— array of market order objects, each containing:order_id— unique identifier for the market orderowner_address— hexadecimal address of the order creatorcreate_time— timestamp when the order was createdsell_token_id— token ID being soldsell_token_quantity— quantity of tokens being soldbuy_token_id— token ID being purchasedbuy_token_quantity— quantity of tokens being purchasedsell_token_quantity_remain— remaining quantity available for salebuy_token_quantity_remain— remaining quantity to be purchasedstate— current order status (typically ACTIVE for this query)
Use case
Thewallet/getmarketorderlistbypair method is used for:
- Building order book displays for trading interfaces.
- Analyzing market depth and liquidity for specific trading pairs.
- Finding matching orders for automated trading strategies.
- Monitoring market activity and order placement patterns.
- Implementing market making and arbitrage detection systems.
curl example
Shell
Body
application/json
TRC10 token ID being sold, as a numeric string (for example, '1000006').
TRC10 token ID being purchased, as a numeric string.
Starting position for pagination (default: 0)
Maximum number of orders to return (default: 20, max: 100)
Optional. Some node builds require visible: true for this endpoint.
Response
200 - application/json
Market orders for trading pair