> ## Documentation Index > Fetch the complete documentation index at: https://docs.hyperprop.com/llms.txt > Use this file to discover all available pages before exploring further. # Get order history (keyset-paginated) > The trader's order history across all their accounts, newest first. Pagination is **keyset-based** (`cursor`), not offset-based: pages are anchored to the last row you received, so new fills landing while you page can never shift rows between pages or skip them. Pass the `nextCursor` from each response to get the next page; `nextCursor: null` means you have everything. Rows voided by a trading-day revert (Time Machine) are excluded. **Example — first page, then next (partner session token):** ```bash curl "https://api.hyperprop.com/platform/v1/user/trading/orders?status=filled&limit=100" \ -H "Authorization: Bearer " curl "https://api.hyperprop.com/platform/v1/user/trading/orders?status=filled&limit=100&cursor=2026-07-13T10:00:35.260Z|8f3593a6-..." \ -H "Authorization: Bearer " ``` **Partner access (read-only).** Approved partner apps can read a trader's journal on the trader's behalf, in either of two ways: - **API key headers** — send `X-Partner-App-Id`, `X-Partner-App-Secret` and the trader's key in `X-Trader-Api-Key`. Optionally add `X-Trader-Email` (must match the key's owner) and `X-Partner-Firm` (limits results to one firm). - **Partner session token** — send the token from `POST /trade/partner/session` as `Authorization: Bearer `. A token created for one firm only returns that firm's accounts. Without a firm, results cover the trader's accounts at every firm. Partner access is read-only: it works on the journal endpoints only. A bad app secret, trader key or email returns `401`; a firm where the trader has no accounts returns `403`; repeated failures return `429`. ## OpenAPI ````yaml /api-reference/openapi.json get /v1/user/trading/orders openapi: 3.0.0 info: title: Hyperprop Platform API version: 1.0.0 description: >- REST API for the Hyperprop Trading Platform — provision evaluation and funded trading accounts, manage traders and plans, react to account lifecycle events via signed webhooks, and reconcile billing. Built for prop firms integrating from their own backend. Authentication, quick start, error handling, idempotency, pagination, custom metadata, webhooks, and the MCP connector are documented at https://docs.hyperprop.com. x-logo: url: https://app.hyperprop.com/logo-icon.svg altText: Hyperprop href: https://hyperprop.com servers: - url: https://api.hyperprop.com/platform description: Production security: [] tags: - name: Trading accounts description: Create, update, and inspect trading accounts. - name: Traders description: Look up and update the traders in your organization. - name: Trading plans description: Define the plans you sell. - name: Trading rules description: Define how accounts are evaluated. - name: Lockouts description: Pause and resume trading on an account. - name: Payouts description: Check payout eligibility and record payouts. - name: Purchases description: Purchases recorded for your organization. - name: Time Machine description: Restore accounts to an earlier trading day or instant. - name: Webhooks description: Register webhook endpoints and inspect deliveries. - name: Events description: Your organization's event history and real-time event stream. - name: Reconciliation description: Balances, end-of-day snapshots, and fills for reconciliation. - name: Analytics description: Organization performance and plan economics. - name: Billing description: 'Your Hyperprop bill: activity, billing cycles, and forecasts.' - name: Team and roles description: Manage dashboard access for your staff. - name: API keys description: Manage your organization's API key. - name: Logs and health description: API request logs, the audit log, and integration health. - name: Organization profile description: Your organization's profile and logo. - name: Support description: Open and follow up on support tickets. - name: Partner access description: >- Read a trader's journal as an approved partner app, with the trader's own key. paths: /v1/user/trading/orders: get: tags: - Partner access summary: Get order history (keyset-paginated) description: >- The trader's order history across all their accounts, newest first. Pagination is **keyset-based** (`cursor`), not offset-based: pages are anchored to the last row you received, so new fills landing while you page can never shift rows between pages or skip them. Pass the `nextCursor` from each response to get the next page; `nextCursor: null` means you have everything. Rows voided by a trading-day revert (Time Machine) are excluded. **Example — first page, then next (partner session token):** ```bash curl "https://api.hyperprop.com/platform/v1/user/trading/orders?status=filled&limit=100" \ -H "Authorization: Bearer " curl "https://api.hyperprop.com/platform/v1/user/trading/orders?status=filled&limit=100&cursor=2026-07-13T10:00:35.260Z|8f3593a6-..." \ -H "Authorization: Bearer " ``` **Partner access (read-only).** Approved partner apps can read a trader's journal on the trader's behalf, in either of two ways: - **API key headers** — send `X-Partner-App-Id`, `X-Partner-App-Secret` and the trader's key in `X-Trader-Api-Key`. Optionally add `X-Trader-Email` (must match the key's owner) and `X-Partner-Firm` (limits results to one firm). - **Partner session token** — send the token from `POST /trade/partner/session` as `Authorization: Bearer `. A token created for one firm only returns that firm's accounts. Without a firm, results cover the trader's accounts at every firm. Partner access is read-only: it works on the journal endpoints only. A bad app secret, trader key or email returns `401`; a firm where the trader has no accounts returns `403`; repeated failures return `429`. operationId: getV1UserTradingOrders parameters: - description: >- `Bearer `: the trader's own session, or a partner session token from `POST /trade/partner/session` name: authorization in: header required: false schema: type: string - description: 'Partner access: your partner app id' x-format: guid: true name: x-partner-app-id in: header required: false schema: type: string - description: 'Partner access: your partner app secret (server-side only)' name: x-partner-app-secret in: header required: false schema: type: string - description: 'Partner access: the trader''s API key (`hpk_...`)' name: x-trader-api-key in: header required: false schema: type: string - description: >- Partner access, optional: the trader's sign-in email; must match the key's owner x-format: email: true name: x-trader-email in: header required: false schema: type: string - description: >- Partner access, optional: organization id, slug or name; limits results to the trader's accounts at that firm name: x-partner-firm in: header required: false schema: type: string - description: Restrict to one trading account x-format: guid: true name: accountId in: query required: false schema: type: string - description: Restrict to one contract (full symbol) name: contract in: query required: false schema: type: string - description: >- Filter by order status (omit for all). partially_filled orders are still working with part of their quantity executed. name: status in: query required: false schema: type: string enum: - filled - partially_filled - cancelled - rejected - description: Page size name: limit in: query schema: type: integer minimum: 1 maximum: 1000 default: 100 - description: Opaque cursor from the previous page's nextCursor name: cursor in: query required: false schema: type: string responses: '200': description: Order history page content: '*/*': schema: $ref: '#/components/schemas/Model392' '400': description: Unknown firm content: '*/*': schema: $ref: '#/components/schemas/Model393' '401': description: Authentication required content: '*/*': schema: $ref: '#/components/schemas/Model9' '403': description: No accounts at this firm for this trader content: '*/*': schema: $ref: '#/components/schemas/Model394' '429': description: Too many failed attempts; retry in a minute content: '*/*': schema: $ref: '#/components/schemas/Model395' '500': description: An unexpected error occurred content: '*/*': schema: $ref: '#/components/schemas/Model5' components: schemas: Model392: type: object properties: success: type: boolean example: true data: $ref: '#/components/schemas/Model391' Model393: type: object properties: success: type: boolean description: Always false on errors example: false statusCode: type: number example: 400 error: type: string example: Bad Request message: type: string example: Unknown firm code: type: string description: Machine-readable error code — switch on this, not on message text example: BAD_REQUEST Model9: type: object properties: success: type: boolean description: Always false on errors example: false statusCode: type: number example: 401 error: type: string example: Unauthorized message: type: string example: Authentication required code: type: string description: Machine-readable error code — switch on this, not on message text example: UNAUTHORIZED Model394: type: object properties: success: type: boolean description: Always false on errors example: false statusCode: type: number example: 403 error: type: string example: Forbidden message: type: string example: No accounts at this firm for this trader code: type: string description: Machine-readable error code — switch on this, not on message text example: FORBIDDEN Model395: type: object properties: success: type: boolean description: Always false on errors example: false statusCode: type: number example: 429 error: type: string example: Too Many Requests message: type: string example: Too many failed attempts; retry in a minute code: type: string description: Machine-readable error code — switch on this, not on message text example: TOO_MANY_REQUESTS Model5: type: object properties: success: type: boolean description: Always false on errors example: false statusCode: type: number example: 500 error: type: string example: Internal Server Error message: type: string example: An unexpected error occurred code: type: string description: Machine-readable error code — switch on this, not on message text example: INTERNAL_ERROR Model391: type: object properties: orders: $ref: '#/components/schemas/orders' nextCursor: type: string example: 2026-07-13T10:00:35.260Z|8f3593a6-ed22-4d3d-bd14-e7d3cd14f5c0 hasMore: type: boolean example: true orders: type: array items: $ref: '#/components/schemas/Model390' Model390: type: object properties: id: type: string account_id: type: string user_id: type: string contract: type: string example: NQU6 product: type: string example: CME symbol: type: string example: NQ side: $ref: '#/components/schemas/Model389' order_type: type: string example: market quantity: type: number example: 1 filled_quantity: type: number example: 1 filled_price: type: number example: 29774 limit_price: type: number stop_price: type: number status: type: string example: filled reject_reason: type: string reason: type: string filled_at: type: string processed_at: type: string updated_at: type: string fee: type: number example: 3 commission: type: number example: 0 realized_pnl: type: number example: 55 Model389: type: string enum: - buy - sell ```` ## Related topics - [Get order history (append-only lifecycle events)](/trade-api/orders/get-order-history-append-only-lifecycle-events.md) - [Get an account's order history](/platform-api/trading-accounts/get-an-accounts-order-history.md) - [Get trade execution history](/trade-api/orders/get-trade-execution-history.md) - [View webhook delivery history](/platform-api/webhooks/view-webhook-delivery-history.md) - [Get all orders (filled, pending, cancelled)](/trade-api/orders/get-all-orders-filled-pending-cancelled.md) This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.