Monitoring Orders
Last updated
Was this helpful?
Last updated
Was this helpful?
Once an order has been successfully created on-chain, its state can be monitored using several available methods, depending on the use case. For a full overview of order states and their transitions, refer to the documentation.
Orders progress through multiple internal states. However, from the perspective of the end-user experience, the following states indicate successful completion:
Fulfilled
SentUnlock
ClaimedUnlock
Any of these states can be treated as successfully completed final state for application-level logic.
Base URL:https://stats-api.dln.trade
Full endpoint reference: and
Examples: See the implementation examples in .
The endpoint retrieves the current state and historical data for all orders associated with a wallet address. This endpoint is also used to populate the trade history view in , which can serve as a reference implementation. Pagination is supported via skip
and take
parameters.
Example:
If multiple orders were created in a single transaction, this endpoint returns data only for the first order.
The response is an array, even if the transaction resulted in only one order:
Example:
Response:
For inspecting a specific order, the endpoint returns full order details as shown on the .
In cases where multiple orders are created in a single transaction, retrieve all order IDs using .
For example, the transaction has been submitted to the BNB Chain. Calling the endpoint:
The orderId
is a deterministic identifier returned in the create-tx
or retrievable via the transaction hash.
An order state can be monitored directly by using .
If set during order creation, the is automatically transferred to the affiliateFeeRecipient
once the order reaches the ClaimedUnlock
status.