Track Delta Order Auction Status
Get Delta Order Auction Status
GET https://api.paraswap.io/delta/orders/:orderId
This endpoint enables users to retrieve real-time details of a specific auction, ensuring transparency and efficient execution monitoring.
Available order statuses (status property)
NOT_STARTED
The initial state of an order when it enters the system. Orders in this state are waiting to be included in a batch auction. Orders that failed execution may also be reset to this state to retry.
RUNNING
Orders that are actively being considered for execution in the current batch auction.
EXECUTING
Orders that have been assigned to a winning agent who has been notified to execute them. This status indicates that on-chain execution is in progress. Orders remain in this state untiltransaction confirmation or timeout.
INSUFFICIENT_BALANCE
This state indicates that an order has insufficient token balance during secondary validation. This happens when a user's token balance drops below the required amount after the initial validation. Since this is a non-terminal status, the system will periodically recheck the balance, allowing the order to proceed to auction if the user adds sufficient funds.
INSUFFICIENT_ALLOWANCE
This state indicates that an order has insufficient token allowance during secondary validation. This occurs when a user's approval for the Delta contract is reduced or revoked after initial validation. Since this is a non-terminal status, the system will periodically recheck the allowance, allowing the order to proceed if the user reinstates or increases the approval.
INVALIDATED
A terminal status indicating that an order has failed secondary validation before being included in an auction. This happens when orders undergo re-validation after initial posting but before auction inclusion. Orders may be invalidated due to changed conditions since initial validation, for example nonce was invalidated because other order with the same nonce has already been executed.
EXECUTED
A terminal state indicating that the order has been successfully executed on-chain.
FAILED
A terminal state indicating that the order failed execution after multiple retry attempts.
EXPIRED
A terminal state indicating that the order's deadline has passed without successful execution.
Available bridge statuses (bridgeStatus property, set only for cross-chain orders, null for same-chain orders).
PENDING
The initial status for a bridged order after execution on the source chain. Indicates that the transaction has been successfully executed on the source chain, but hasn't been bridged yet.
FILLED
A terminal state indicating that the order has been filled on the destination chain. fillTx property in bridgeMetadata becomes available.
REFUNDED
A terminal state indicating that the order has been refunded on the source chain. The refunded token would be the one that was sent to bridge after the swap. depositRefundTxHash property in bridgeMetadata becomes available.
Get Delta Orders for a User
GET https://api.paraswap.io/delta/orders
The Get Delta Orders for a User endpoint allows integrators to fetch all orders associated with a specific address, making it invaluable for dashboards, trade history tracking, and compliance purposes.
Query Parameters
userAddress*
string
User Address.
chainId
string
Filters orders by Chain ID.
page
integer
Default: 1.
limit
integer
Default: 100.
Most common error messages
These are the two most common messages when using this endpoint.
ValidationError- validation for params failedUnsupportedChain- the chain ID is not supported by Delta.
To avoid running into ValidationError and UnsupportedChain errors when using this endpoint, here are some recommendations:
Avoiding ValidationError
ValidationErrorCheck Required Parameters: Ensure all mandatory parameters are included in your request. Missing or incorrectly formatted fields often trigger this error.
Validate Data Types: Confirm that parameters match the expected types (e.g., numbers vs. strings, correct JSON structure).
Follow API Documentation: Double-check the expected format for each parameter in the official API documentation.
Avoiding UnsupportedChain
UnsupportedChainVerify Supported Chains: Check the API documentation or a dedicated "supported chains" endpoint to ensure the chain ID is compatible with Delta.
Use Correct Chain IDs: Some APIs require chain IDs in decimal format, while others expect hex. Ensure you’re using the correct format.
Last updated