> ## 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: 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}/activity: get: tags: - Trading accounts 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/Model434' '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/Model435' '404': description: Not Found - No account exists with this ID content: '*/*': schema: $ref: '#/components/schemas/Model436' '500': description: An unexpected error occurred content: '*/*': schema: $ref: '#/components/schemas/Model5' security: - X-API-Key: [] components: schemas: Model434: type: object properties: success: type: boolean example: true data: $ref: '#/components/schemas/Model433' 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 Model435: 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 Model436: 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 Model433: 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/Model430' sessions: $ref: '#/components/schemas/sessions' devices: $ref: '#/components/schemas/devices' Model430: type: array items: $ref: '#/components/schemas/Model429' sessions: type: array items: $ref: '#/components/schemas/Model431' devices: type: array items: $ref: '#/components/schemas/Model432' Model429: 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/Model428' createdAt: type: string Model431: 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 Model432: 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 Model428: 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 - [Introduction](/introduction.md) - [View webhook delivery history](/platform-api/webhooks/view-webhook-delivery-history.md) - [List API request logs](/platform-api/logs-and-health/list-api-request-logs.md) - [Get order history (append-only lifecycle events)](/trade-api/orders/get-order-history-append-only-lifecycle-events.md) - [Get order history (keyset-paginated)](/platform-api/partner-access/get-order-history-keyset-paginated.md) This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.