POST
/
95e61622bf6a8af293978377718e3b77
/
wallet
/
getmarketorderbyid
wallet/getmarketorderbyid
curl --request POST \
  --url https://tron-mainnet.core.chainstack.com/95e61622bf6a8af293978377718e3b77/wallet/getmarketorderbyid \
  --header 'Content-Type: application/json' \
  --data '{
  "order_id": "0x1234567890abcdef1234567890abcdef12345678"
}'
{
  "order_id": "<string>",
  "owner_address": "<string>",
  "create_time": 123,
  "sell_token_id": "<string>",
  "sell_token_quantity": "<string>",
  "buy_token_id": "<string>",
  "buy_token_quantity": "<string>",
  "sell_token_quantity_remain": "<string>",
  "buy_token_quantity_remain": "<string>",
  "state": "<string>",
  "prev": "<string>",
  "next": "<string>"
}
TRON API method that retrieves detailed information for a specific market order by its unique order ID. This provides comprehensive details about order status, quantities, and trading pair information.
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

  • order_id — unique identifier of the market order to query (as hexadecimal string)

​
Response

  • order_id — unique identifier for the market order
  • owner_address — hexadecimal address of the order creator
  • create_time — timestamp when the order was created
  • sell_token_id — token ID being sold (empty for TRX)
  • sell_token_quantity — original quantity of tokens being sold
  • buy_token_id — token ID being purchased (empty for TRX)
  • buy_token_quantity — original quantity of tokens being purchased
  • sell_token_quantity_remain — remaining quantity available for sale
  • buy_token_quantity_remain — remaining quantity to be purchased
  • state — current order status (ACTIVE, INACTIVE, CANCELED, etc.)
  • prev — previous order ID in the order book (if applicable)
  • next — next order ID in the order book (if applicable)

​
Use case

The wallet/getmarketorderbyid method is used for:
  • Checking the current status and execution progress of a specific order.
  • Monitoring order fulfillment and remaining quantities.
  • Building order tracking interfaces for trading applications.
  • Verifying order details before attempting modifications or cancellations.
  • Investigating order book structure and linked order relationships.
The prev and next fields help navigate the order book structure, showing how orders are linked in the matching system. Empty token IDs represent TRX in trading pairs. Order states indicate the current execution status and availability for matching.

Body

application/json

Response

200 - application/json

Market order details

The response is of type object.