RULE CHANGE
Pagination
Article clarifies that cursor pagination applies to TWAP and VWAP order history endpoints and simplifies cursor position description.
What this means
The cursor pattern now applies to completed or canceled TWAP and VWAP orders via GET /v1/twap-orders in addition to filled orders, closed positions, and scaled orders. The description of how cursors preserve position changed from "exact position in Convex's compound index" to "exact sort position". All other cursor rules stayed the same.
▸ View exact changes
What the page said before and after
Before Oct 11, 2026
Source: https://docs.myfundedperpetuals.com/pagination
Walk recent order history with a bounded opaque cursor.
GET /v1/orders returns newest orders first. Set limit from 1 to 100; the
default is 50.
When has_more is true, send next_cursor as the next request's cursor
parameter. Treat the cursor as opaque and URL-encode it:
bash theme={null}
curl --get "https://developers.myfundedperpetuals.com/v1/orders"
-H "Authorization: Bearer $FP_API_KEY"
--data-urlencode "account_id=ACCOUNT_ID"
--data-urlencode "limit=50"
--data-urlencode "cursor=$NEXT_CURSOR"
− The same cursor pattern is used by filled orders, closed positions, and scaled
− orders. Each endpoint returns its own opaque cursor. Never reuse a cursor with
a different endpoint, account, or filter.
− The opaque cursor preserves the exact position in Convex's compound index, so
− orders sharing the same millisecond are not skipped. The server reads at most
limit indexed rows for each page, regardless of the account's total order
history.
A client_order_id lookup is not paginated. Send
GET /v1/orders?client_order_id=... to receive the normal page shape with zero
or one order and has_more: false. Do not send limit or cursor with that
lookup.
After Oct 15, 2026
Source: https://docs.myfundedperpetuals.com/pagination
Walk recent order history with a bounded opaque cursor.
GET /v1/orders returns newest orders first. Set limit from 1 to 100; the
default is 50.
When has_more is true, send next_cursor as the next request's cursor
parameter. Treat the cursor as opaque and URL-encode it:
bash theme={null}
curl --get "https://developers.myfundedperpetuals.com/v1/orders"
-H "Authorization: Bearer $FP_API_KEY"
--data-urlencode "account_id=ACCOUNT_ID"
--data-urlencode "limit=50"
--data-urlencode "cursor=$NEXT_CURSOR"
+ The same cursor pattern is used by filled orders, closed positions, scaled
+ orders, and completed or canceled TWAP and VWAP history (GET /v1/twap-orders
+ with a status of completed or canceled). Each endpoint returns its own opaque cursor. Never reuse a cursor with
a different endpoint, account, or filter.
+ The opaque cursor preserves the exact sort position, so orders sharing the same millisecond are not skipped. The server reads at most
limit indexed rows for each page, regardless of the account's total order
history.
A client_order_id lookup is not paginated. Send
GET /v1/orders?client_order_id=... to receive the normal page shape with zero
or one order and has_more: false. Do not send limit or cursor with that
lookup.
Source: https://docs.myfundedperpetuals.com/pagination
Walk recent order history with a bounded opaque cursor.
GET /v1/orders returns newest orders first. Set limit from 1 to 100; the
default is 50.
When has_more is true, send next_cursor as the next request's cursor
parameter. Treat the cursor as opaque and URL-encode it:
bash theme={null}
curl --get "https://developers.myfundedperpetuals.com/v1/orders"
-H "Authorization: Bearer $FP_API_KEY"
--data-urlencode "account_id=ACCOUNT_ID"
--data-urlencode "limit=50"
--data-urlencode "cursor=$NEXT_CURSOR"
− The same cursor pattern is used by filled orders, closed positions, and scaled
− orders. Each endpoint returns its own opaque cursor. Never reuse a cursor with
+ The same cursor pattern is used by filled orders, closed positions, scaled
+ orders, and completed or canceled TWAP and VWAP history (GET /v1/twap-orders
+ with a status of completed or canceled). Each endpoint returns its own opaque cursor. Never reuse a cursor with
a different endpoint, account, or filter.
− The opaque cursor preserves the exact position in Convex's compound index, so
− orders sharing the same millisecond are not skipped. The server reads at most
+ The opaque cursor preserves the exact sort position, so orders sharing the same millisecond are not skipped. The server reads at most
limit indexed rows for each page, regardless of the account's total order
history.
A client_order_id lookup is not paginated. Send
GET /v1/orders?client_order_id=... to receive the normal page shape with zero
or one order and has_more: false. Do not send limit or cursor with that
lookup.