> ## 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 event log and session history > Everything support staff need to investigate one account without pulling logs by hand: - **events** — the account's event log (`ACCOUNT_CREATED`, `STATUS_CHANGED`, `ACCOUNT_FAILED` with the violated rule, `LOCKOUT_CREATED`, `PURCHASE_CREATED`, `FILL_CREATED`, …). Same rows as `GET /organization/events?accountId=`, newest first, without the bulky payload snapshot. - **sessions** — the account owner's sign-in and security history: successful and failed logins (with IP, user agent and sign-in method), password resets, MFA enabled/disabled, agreement signatures, market-data grants. - **devices** — devices the owner has used for market data (web / mobile), with first/last seen and whether the device session is still active. The account must belong to your organization; `sessions` and `devices` cover that account's owner only. ```bash curl -X GET "https://api.hyperprop.com/platform/v1/organization/trading-accounts/7c9e6679-7425-40de-944b-e07fc1f90ae7/activity?limit=100" \ -H "X-API-Key: hp_live_your_key_here" ``` ## OpenAPI ````yaml /api-reference/openapi.json get /v1/organization/trading-accounts/{accountId}/activity 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: Authentication description: >- User authentication - signup, signin, signout, password reset, email verification, OAuth, and MFA - name: User description: >- User account management - profile, notifications, agreements, dismissals, and audit logs. Requires Bearer token. - name: Organization description: >- Organization management - profile, team, trading accounts, plans, and rules. Supports **dual authentication**: Bearer JWT token (dashboard users) OR X-API-Key (programmatic access). - name: Market Data description: CME futures contracts and market data. Requires Bearer token. - name: Indicator Builder description: >- AI-assisted authoring of custom Hyperprop Script indicators for the web terminal. Requires Bearer token. - name: System description: System endpoints - health checks and connectivity paths: /v1/organization/trading-accounts/{accountId}/activity: get: tags: - Organization summary: Get an account's event log and session history description: >- Everything support staff need to investigate one account without pulling logs by hand: - **events** — the account's event log (`ACCOUNT_CREATED`, `STATUS_CHANGED`, `ACCOUNT_FAILED` with the violated rule, `LOCKOUT_CREATED`, `PURCHASE_CREATED`, `FILL_CREATED`, …). Same rows as `GET /organization/events?accountId=`, newest first, without the bulky payload snapshot. - **sessions** — the account owner's sign-in and security history: successful and failed logins (with IP, user agent and sign-in method), password resets, MFA enabled/disabled, agreement signatures, market-data grants. - **devices** — devices the owner has used for market data (web / mobile), with first/last seen and whether the device session is still active. The account must belong to your organization; `sessions` and `devices` cover that account's owner only. ```bash curl -X GET "https://api.hyperprop.com/platform/v1/organization/trading-accounts/7c9e6679-7425-40de-944b-e07fc1f90ae7/activity?limit=100" \ -H "X-API-Key: hp_live_your_key_here" ``` operationId: getV1OrganizationTradingaccountsAccountidActivity parameters: - description: The account whose activity to retrieve x-format: guid: true name: accountId in: path required: true schema: type: string - description: >- Maximum events and maximum session entries to return (each, newest first) name: limit in: query schema: type: integer minimum: 1 maximum: 500 default: 100 responses: '200': description: Success - Returns the account activity content: '*/*': schema: $ref: '#/components/schemas/Model396' '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/Model397' '404': description: Not Found - No account exists with this ID content: '*/*': schema: $ref: '#/components/schemas/Model398' '500': description: An unexpected error occurred content: '*/*': schema: $ref: '#/components/schemas/Model5' security: - Bearer: [] - X-API-Key: [] components: schemas: Model396: type: object properties: success: type: boolean example: true data: $ref: '#/components/schemas/Model395' 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 Model397: 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 Model398: 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 Model395: type: object properties: accountId: type: string x-format: guid: true userId: type: string description: The account owner; null when the account is not linked to a user x-format: guid: true events: $ref: '#/components/schemas/Model392' sessions: $ref: '#/components/schemas/sessions' devices: $ref: '#/components/schemas/devices' Model392: type: array items: $ref: '#/components/schemas/Model391' sessions: type: array items: $ref: '#/components/schemas/Model393' devices: type: array items: $ref: '#/components/schemas/Model394' Model391: type: object properties: id: type: string eventType: type: string example: ACCOUNT_FAILED reason: type: string example: 'Max drawdown breached: equity 47,950.00 below floor 48,000.00' metadata: $ref: '#/components/schemas/Model390' createdAt: type: string Model393: type: object properties: id: type: string action: type: string example: login_success description: type: string ipAddress: type: string example: 203.0.113.7 userAgent: type: string method: type: string example: password createdAt: type: string Model394: type: object properties: id: type: string deviceId: type: string deviceType: type: string example: web userAgent: type: string ipAddress: type: string firstSeenAt: type: string lastSeenAt: type: string isActive: type: boolean Model390: type: object securitySchemes: Bearer: type: apiKey name: Authorization in: header description: >- JWT Bearer token for user session auth. Format: "Bearer {token}". Used by User and Organization endpoints. X-API-Key: type: apiKey name: X-API-Key in: header description: >- Organization API key for programmatic access. Format: "hp_live_{key}". Used by Organization endpoints as an alternative to Bearer token. Keys are managed in the dashboard. ```` ## Related topics - [View webhook delivery history](/platform-api/organization/view-webhook-delivery-history.md) - [Changelog](/changelog.md) - [Get audit logs](/platform-api/user/get-audit-logs.md) - [Real-time event stream (WebSocket)](/platform-api/organization/real-time-event-stream-websocket.md) - [Get order history from database (append-only lifecycle events)](/trade-api/orders/get-order-history-from-database-append-only-lifecycle-events.md)