Pagination - ParlayX

Order lists return a page of results plus a nextPageToken cursor. The pagination helpers follow that cursor for you and yield individual orders, so you can iterate the full history without handling tokens yourself.

from parlayx import ParlayX, paginate_kalshi_orders, paginate_polymarket_orders

client = ParlayX()

for order in paginate_polymarket_orders(client, status="OPEN"):
    print(order.order_id, order.status)

for order in paginate_kalshi_orders(client, status="FILLED"):
    print(order.order_id, order.status)

import {
  createClient,
  paginateKalshiOrders,
  paginatePolymarketOrders,
} from "@parlayx/sdk";

const client = createClient({
  keyId: process.env.PARLAYX_KEY_ID!,
  privateKeyHex: process.env.PARLAYX_PRIVATE_KEY_HEX!,
});

for await (const order of paginatePolymarketOrders(client, { status: "OPEN" })) {
  console.log(order.orderId, order.status);
}

for await (const order of paginateKalshiOrders(client, { status: "FILLED" })) {
  console.log(order.orderId, order.status);
}

Both helpers accept the same filters as their list endpoint minus the page cursor, and stop automatically once the last page is reached. Each request still raises a RequestError on failure. If you need raw pages or the nextPageToken directly, call the list method instead.

page = client.kalshi.list_orders(page_size=50)
print(len(page.orders), page.next_page_token)

const page = await client.kalshi.listOrders({ pageSize: 50 });
console.log(page.orders.length, page.nextPageToken);

Async in Python

The synchronous helpers are generators, so they work with a plain for. The async client has its own pair, apaginate_kalshi_orders and apaginate_polymarket_orders, which are async generators:

from parlayx import AsyncParlayX, apaginate_kalshi_orders

async with AsyncParlayX() as client:
    async for order in apaginate_kalshi_orders(client, status="FILLED"):
        print(order.order_id, order.status)

Passing an AsyncParlayX to the synchronous helper does not work, and passing a ParlayX to the async one does not either. The four names exist so the pairing is explicit rather than inferred at runtime.

What is not cursored

Positions and fills return their full result in one call, so they have no helper: listPositions() and getOrderFills(orderId) in TypeScript, list_positions() and get_order_fills(order_id) in Python.