KERNELFLOW / DEVELOPERS

List orders

Find a sender’s orders and recover an order after an uncertain submission response.

GET/v1/ordersAPI key required

Parameter	Required	Description
address	Yes	Sender address (fromAddress), not the recipient.
limit	No	Integer 1–100; default 20.
status	No	Filter by Pending, Succeeded, Failed, Refunded, or WaitVerify.
cursor	No	Opaque nextCursor from the previous response.

Request

curl --get 'https://api.kernelflow.org/v1/orders' \
  --header "X-API-Key: $AGGREGATOR_API_KEY" \
  --data-urlencode "address=$USER_ADDRESS" \
  --data-urlencode 'limit=20' \
  --data-urlencode 'status=Pending'

Response · illustrative

{
  "code": 0,
  "msg": "success",
  "data": {
    "items": [
      {
        "orderId": "ord_example",
        "status": "Pending",
        "fromTxHash": "0x...",
        "createdAt": 1793942831,
        "updatedAt": 1793942831
      }
    ],
    "nextCursor": ""
  }
}

Results are newest first and are selected by sender address across API keys. Do not treat this as a key-scoped private history. Your product should retain its own order records and enforce its own user access controls.

For the next page, pass nextCursor as cursor with the same address and status filter. An empty nextCursor marks the end. Each item uses the Get an order response shape, including optional fields.