GET /v1/orders
The public gateway requires a server API key for order history.
The subject selects the user’s submissions within the authenticated tenant.
This endpoint lists POST /order/openfor submissions.
It does not list open-flow registrations from POST /order.
For delegated requests, compare the returned subject with the requested subject.
Reject a response with a different subject.
Pagination
Uselimit to request a page size.
The default is 100 entries. The maximum is 500 entries.
Start with GET /orders?cursor=&limit=100.
The explicit empty cursor selects cursor pagination.
Use the returned nextCursor unchanged for the next request.
Do not combine cursor with since.
Do not reconstruct cursors from timestamps.
Without cursor, the endpoint returns a legacy page without nextCursor.
Cursor pages follow recorded submission order.
Recent rows can appear again because the cursor preserves a safety interval.
Remove duplicate rows by orderId.
A page shorter than limit means that the reader has reached the current end.
Current order state
Rows combine submission identifiers with the available chain record. UseonchainOrderId for the on-chain views.
The chain record can include source transaction, inputs, outputs, lifecycle state, and refund information.
The row’s state is the initial upstream state and does not change.
Use lifecycle and chain.status for current progress.
The stored projection sets refundRequiresOnchainCheck to true.
Check the escrow before presenting a refund as executable.
Read the effective escrow deadline when an extension is possible.
A missing chain record can mean that the observer has not recorded the Open event yet.
It does not establish that the wallet transaction failed.