> ## 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 event timeline > Every step of every order on one account, newest first: the order being submitted, accepted, modified, cancelled, filled or rejected, with the time each step happened. Use it to see what a trader did and when — for example, to check whether they tried to close a position or cancel an order before a fill. Each event carries: - **action** — a readable summary, e.g. `Close position requested by trader`, `Order modified`, `Cancelled by trader`, `Position closed by trader`, `Rejected: Order would exceed max contracts limit`. - **initiatedBy** — who started the order: `trader`, `automatic` (risk rules, brackets, market close), `admin` (your firm's staff), `copy_trading`, or `null` when it cannot be determined. - **orderId** — the same ID as `id` / `orderId` in `GET /organization/trading-accounts/{accountId}/orders`; pass it as `orderId` here to see one order's full lifecycle. - **reason** / **rejectReason** — the recorded text. `reason` describes the order as a whole, so it repeats on every event of that order. - **occurredAt** — when this step happened (UTC). Page with `pagination.nextCursor`. A cancel or modify request from the trader appears as its own event, followed by the outcome (`cancelled`, `accepted` after a modify, or `rejected`). ```bash curl -X GET "https://api.hyperprop.com/platform/v1/organization/trading-accounts/7c9e6679-7425-40de-944b-e07fc1f90ae7/order-events?from=2026-10-07T00:00:00Z&eventType=submit_requested,cancelled,fill_final" \ -H "X-API-Key: hp_live_your_key_here" ``` ## OpenAPI ````yaml /api-reference/openapi.json get /v1/organization/trading-accounts/{accountId}/order-events 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}/order-events: get: tags: - Trading accounts summary: Get an account's order event timeline description: >- Every step of every order on one account, newest first: the order being submitted, accepted, modified, cancelled, filled or rejected, with the time each step happened. Use it to see what a trader did and when — for example, to check whether they tried to close a position or cancel an order before a fill. Each event carries: - **action** — a readable summary, e.g. `Close position requested by trader`, `Order modified`, `Cancelled by trader`, `Position closed by trader`, `Rejected: Order would exceed max contracts limit`. - **initiatedBy** — who started the order: `trader`, `automatic` (risk rules, brackets, market close), `admin` (your firm's staff), `copy_trading`, or `null` when it cannot be determined. - **orderId** — the same ID as `id` / `orderId` in `GET /organization/trading-accounts/{accountId}/orders`; pass it as `orderId` here to see one order's full lifecycle. - **reason** / **rejectReason** — the recorded text. `reason` describes the order as a whole, so it repeats on every event of that order. - **occurredAt** — when this step happened (UTC). Page with `pagination.nextCursor`. A cancel or modify request from the trader appears as its own event, followed by the outcome (`cancelled`, `accepted` after a modify, or `rejected`). ```bash curl -X GET "https://api.hyperprop.com/platform/v1/organization/trading-accounts/7c9e6679-7425-40de-944b-e07fc1f90ae7/order-events?from=2026-10-07T00:00:00Z&eventType=submit_requested,cancelled,fill_final" \ -H "X-API-Key: hp_live_your_key_here" ``` operationId: getV1OrganizationTradingaccountsAccountidOrderevents parameters: - description: The account whose order events to retrieve x-format: guid: true name: accountId in: path required: true schema: type: string - description: Only events at or after this time (ISO 8601) x-format: isoDate: true name: from in: query required: false schema: type: string - description: Only events at or before this time (ISO 8601) x-format: isoDate: true name: to in: query required: false schema: type: string - description: >- Comma-separated event types to include. One or more of: planned, submit_requested, validated, accepted, replace_requested, cancel_requested, fill_partial, fill_final, cancelled, rejected, expired, bracket_auto_resized. Default: all name: eventType in: query required: false schema: type: string pattern: >- ^(planned|submit_requested|validated|accepted|replace_requested|cancel_requested|fill_partial|fill_final|cancelled|rejected|expired|bracket_auto_resized)(,(planned|submit_requested|validated|accepted|replace_requested|cancel_requested|fill_partial|fill_final|cancelled|rejected|expired|bracket_auto_resized))*$ - description: >- Only events of this order (the `orderId` from this endpoint or `id` / `orderId` from the orders endpoint) x-format: guid: true name: orderId in: query required: false schema: type: string - description: >- Include events voided by a Time Machine revert (they carry revertedAt) name: includeReverted in: query schema: type: boolean default: false - description: >- Pass `pagination.nextCursor` from the previous response to get the next (older) page name: cursor in: query required: false schema: type: string - name: limit in: query schema: type: integer minimum: 1 maximum: 500 default: 100 responses: '200': description: Success - Returns the account's order events, newest first content: '*/*': schema: $ref: '#/components/schemas/Model427' '400': description: Invalid cursor content: '*/*': schema: $ref: '#/components/schemas/Model428' '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/Model429' '404': description: Not Found - No account exists with this ID content: '*/*': schema: $ref: '#/components/schemas/Model430' '500': description: An unexpected error occurred content: '*/*': schema: $ref: '#/components/schemas/Model5' security: - X-API-Key: [] components: schemas: Model427: type: object properties: success: type: boolean example: true data: $ref: '#/components/schemas/Model426' Model428: 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: Invalid cursor code: type: string description: Machine-readable error code — switch on this, not on message text example: INVALID_CURSOR 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 Model429: 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 Model430: 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 Model426: type: object properties: accountId: type: string example: 7c9e6679-7425-40de-944b-e07fc1f90ae7 x-format: guid: true events: $ref: '#/components/schemas/Model424' pagination: $ref: '#/components/schemas/Model425' Model424: type: array items: $ref: '#/components/schemas/Model423' Model425: type: object properties: limit: type: number example: 100 hasMore: type: boolean example: true nextCursor: type: string example: >- eyJlbmdpbmVfdXBkYXRlZF9hdCI6IjIwMjYtMTAtMDdUMTQ6MzI6MTAuNTEyMzQ1KzAwOjAwIiwiaWQiOiJhYmMifQ Model423: type: object properties: id: type: string description: Event ID example: b1e4f0a2-5c3d-4e8f-9a7b-1d2c3e4f5a6b x-format: guid: true orderId: type: string example: 3f2b8c1e-9d4a-4e7b-8a61-0c5d2e9f7a10 x-format: guid: true eventType: $ref: '#/components/schemas/eventType' action: type: string example: Close position requested by trader initiatedBy: $ref: '#/components/schemas/initiatedBy' status: type: string description: Order status right after this event example: pending_submit contract: type: string example: ESZ6 product: type: string example: CME symbol: type: string example: ES side: type: string example: sell orderType: type: string example: market quantity: type: number example: 2 filledQuantity: type: number description: Cumulative filled quantity after this event example: 0 limitPrice: type: number example: null stopPrice: type: number example: null filledPrice: type: number description: Average fill price so far example: null lastFillPrice: type: number description: Price of the fill this event records (fill events) example: null lastFillQuantity: type: number description: Quantity of the fill this event records (fill events) example: null reason: type: string example: User closed position ESZ6 rejectReason: type: string example: null occurredAt: type: string example: '2026-10-07T14:32:10.512345+00:00' revertedAt: type: string example: null eventType: type: string example: submit_requested enum: - planned - submit_requested - validated - accepted - replace_requested - cancel_requested - fill_partial - fill_final - cancelled - rejected - expired - bracket_auto_resized initiatedBy: type: string example: trader enum: - trader - automatic - admin - copy_trading 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 (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 an account's event log and session history](/platform-api/trading-accounts/get-an-accounts-event-log-and-session-history.md) - [Changelog](/changelog.md) - [Real-time WebSocket for trading events](/trade-api/websocket/real-time-websocket-for-trading-events.md) This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.