> ## 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 an account's order history > Every order the engine recorded for one account — filled, working, cancelled, rejected or expired — newest first, across all trading days. Each row carries the engine's free-text `reason` and the derived `trigger` / `triggerLabel` (see the fills endpoint), plus realized P&L, fees, bracket links and the account balance after the fill. Use `GET /organization/snapshots/fills` for a whole-organization, one-trading-day view; use this endpoint for one account's history. ```bash curl -X GET "https://api.hyperprop.com/platform/v1/organization/trading-accounts/7c9e6679-7425-40de-944b-e07fc1f90ae7/orders?limit=100" \ -H "X-API-Key: hp_live_your_key_here" ``` ## OpenAPI ````yaml /api-reference/openapi.json get /v1/organization/trading-accounts/{accountId}/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/organization/trading-accounts/{accountId}/orders: get: tags: - Trading accounts summary: Get an account's order history description: >- Every order the engine recorded for one account — filled, working, cancelled, rejected or expired — newest first, across all trading days. Each row carries the engine's free-text `reason` and the derived `trigger` / `triggerLabel` (see the fills endpoint), plus realized P&L, fees, bracket links and the account balance after the fill. Use `GET /organization/snapshots/fills` for a whole-organization, one-trading-day view; use this endpoint for one account's history. ```bash curl -X GET "https://api.hyperprop.com/platform/v1/organization/trading-accounts/7c9e6679-7425-40de-944b-e07fc1f90ae7/orders?limit=100" \ -H "X-API-Key: hp_live_your_key_here" ``` operationId: getV1OrganizationTradingaccountsAccountidOrders parameters: - x-format: guid: true name: accountId in: path required: true schema: type: string - description: >- Comma-separated order statuses to include (e.g. filled, pending, cancelled, rejected, expired). Default: all name: status in: query required: false schema: type: string - description: >- Include orders voided by a Time Machine revert (they carry revertedAt) name: includeReverted in: query schema: type: boolean default: false - name: limit in: query schema: type: integer minimum: 1 maximum: 500 default: 100 - name: offset in: query schema: type: integer minimum: 0 default: 0 responses: '200': description: Success - Returns the account's orders content: '*/*': schema: $ref: '#/components/schemas/Model425' '401': description: Authentication required content: '*/*': schema: $ref: '#/components/schemas/Model9' '403': description: Forbidden - This account belongs to a different organization content: '*/*': schema: $ref: '#/components/schemas/Model426' '404': description: Not Found - No account exists with this ID content: '*/*': schema: $ref: '#/components/schemas/Model427' '500': description: An unexpected error occurred content: '*/*': schema: $ref: '#/components/schemas/Model5' security: - X-API-Key: [] components: schemas: Model425: type: object properties: success: type: boolean example: true data: $ref: '#/components/schemas/Model424' 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 Model426: type: object properties: statusCode: type: number example: 403 error: type: string example: Forbidden message: type: string example: This account does not belong to your organization code: type: string example: ACCOUNT_NOT_IN_ORG Model427: type: object properties: statusCode: type: number example: 404 error: type: string example: Not Found message: type: string example: Trading account not found code: type: string example: ACCOUNT_NOT_FOUND 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 Model424: type: object properties: accountId: type: string x-format: guid: true orders: $ref: '#/components/schemas/Model422' pagination: $ref: '#/components/schemas/Model423' Model422: type: array items: $ref: '#/components/schemas/Model421' Model423: type: object properties: total: type: number limit: type: number offset: type: number hasMore: type: boolean Model421: type: object properties: id: type: string contract: type: string example: ESH6 product: type: string example: CME symbol: type: string example: ES side: type: string example: sell orderType: type: string example: market status: type: string example: filled quantity: type: number filledQuantity: type: number limitPrice: type: number stopPrice: type: number filledPrice: type: number realizedPnl: type: number fee: type: number commission: type: number balanceAfter: type: number description: Account balance right after this fill, as stamped by the engine bracketType: type: string bracketParentId: type: string plannedTakeProfit: type: number plannedStopLoss: type: number reason: type: string rejectReason: type: string trigger: type: string example: auto_liquidation_breach triggerLabel: type: string example: 'Auto Liquidation: Breach' processedAt: type: string filledAt: type: string updatedAt: type: string revertedAt: type: string securitySchemes: X-API-Key: type: apiKey name: X-API-Key in: header description: >- Organization API key. Format: "hp_live_{key}". Organization admins manage the key in the dashboard. ```` ## Related topics - [Get order history (keyset-paginated)](/platform-api/partner-access/get-order-history-keyset-paginated.md) - [Get order history (append-only lifecycle events)](/trade-api/orders/get-order-history-append-only-lifecycle-events.md) - [Get account change history](/platform-api/trading-accounts/get-account-change-history.md) - [Get an account's event log and session history](/platform-api/trading-accounts/get-an-accounts-event-log-and-session-history.md) - [Get trade execution history](/trade-api/orders/get-trade-execution-history.md) This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.