> ## 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 account change history > Get the audit trail of all changes made to a trading account. Shows who changed what, when, and why - including both single updates and bulk operations. **Example response:** ```json { "accountId": "...", "changes": [ { "id": "...", "adminEmail": "admin@example.com", "batchId": null, "changes": { "status": { "old": "in_progress", "new": "failed" }, "currentBalance": { "old": 52000, "new": 49500 } }, "reason": "Max loss exceeded", "createdAt": "2026-02-17T14:30:00Z" } ] } ``` ## OpenAPI ````yaml /api-reference/openapi.json get /v1/organization/trading-accounts/{accountId}/changes 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}/changes: get: tags: - Trading accounts summary: Get account change history description: >- Get the audit trail of all changes made to a trading account. Shows who changed what, when, and why - including both single updates and bulk operations. **Example response:** ```json { "accountId": "...", "changes": [ { "id": "...", "adminEmail": "admin@example.com", "batchId": null, "changes": { "status": { "old": "in_progress", "new": "failed" }, "currentBalance": { "old": 52000, "new": 49500 } }, "reason": "Max loss exceeded", "createdAt": "2026-02-17T14:30:00Z" } ] } ``` operationId: getV1OrganizationTradingaccountsAccountidChanges parameters: - description: The trading account ID x-format: guid: true name: accountId in: path required: true schema: type: string - description: Results per page name: limit in: query schema: type: integer minimum: 1 maximum: 100 default: 50 - description: Offset for pagination name: offset in: query schema: type: integer minimum: 0 default: 0 - description: >- Cursor for pagination. Pass the `nextCursor` value from the previous response to get the next page. When using cursor, do not send `offset` — it will be ignored. **How it works:** The cursor is an opaque string that points to the last item you received. The server uses it to efficiently fetch the next set of results without scanning previous pages. **Backwards compatible:** If you don't send a cursor, offset/limit pagination works as before. name: cursor in: query required: false schema: type: string responses: '200': description: Change history retrieved content: '*/*': schema: $ref: '#/components/schemas/Model419' '401': description: Authentication required content: '*/*': schema: $ref: '#/components/schemas/Model9' '404': description: Account not found content: '*/*': schema: $ref: '#/components/schemas/Model420' '500': description: An unexpected error occurred content: '*/*': schema: $ref: '#/components/schemas/Model5' security: - X-API-Key: [] components: schemas: Model419: type: object properties: success: type: boolean example: true data: $ref: '#/components/schemas/Model418' 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 Model420: type: object properties: statusCode: type: number example: 404 error: type: string example: Not Found message: type: string example: 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 Model418: type: object example: accountId: 7c9e6679-7425-40de-944b-e07fc1f90ae7 changes: - id: b1c2d3e4-f5a6-7890-abcd-ef1234567890 adminEmail: admin@propfirm.com batchId: null changes: currentBalance: old: 50000 new: 51250 reason: 'Customer support ticket #4521 - balance correction' createdAt: '2026-02-17T14:30:00.000Z' - id: c2d3e4f5-a6b7-8901-bcde-f12345678901 adminEmail: admin@propfirm.com batchId: e4f5a6b7-c8d9-0123-efab-456789012345 changes: status: old: failed new: in_progress currentBalance: old: 48500 new: 50000 reason: Server maintenance compensation - bulk reset createdAt: '2026-02-16T09:15:00.000Z' pagination: total: 2 limit: 50 offset: 0 hasMore: false properties: accountId: type: string x-format: guid: true changes: $ref: '#/components/schemas/Model416' pagination: $ref: '#/components/schemas/Model417' Model416: type: array items: $ref: '#/components/schemas/Model415' Model417: type: object properties: total: type: number limit: type: number offset: type: number hasMore: type: boolean nextCursor: type: string description: >- Cursor for the next page. Pass as ?cursor= to get the next set of results. Null if no more results. Model415: type: object properties: id: type: string x-format: guid: true adminEmail: type: string batchId: type: string x-format: guid: true changes: $ref: '#/components/schemas/changes' reason: type: string createdAt: type: string changes: type: object 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 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) - [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 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.