> ## 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 end-of-day account snapshots

> Returns every account that traded during a CME trading day, with their end-of-day balances and performance.

**Produced once per trading day**, shortly after market close.

**What you get per account:**
- Starting and ending balances
- Daily P&L and total P&L
- High water mark
- Fill count and contracts traded
- Status changes and violation reasons

**CME trading day:** 17:00 CT previous day → 16:00 CT current day.

**Server-side account scoping:**
Pass `?accountId=<uuid>` or `?accountId=<uuid>,<uuid>,...` (up to 100) to
retrieve snapshots for exactly the accounts you care about — no need to pull
the whole org and filter locally. Useful for multi-tenant setups where each
tenant maps to a subset of accounts. IDs outside your organization return
`404 ACCOUNT_NOT_FOUND`, so the scoping is safe by construction.

**Knowing when snapshots are ready:**
The response includes `latestCompletedTradingDay` — the most recent trading
day for which EOD snapshots exist for your organization. Poll it, or better:
subscribe to the `snapshot.ready` webhook event, which fires once per
organization per trading day the moment the EOD batch is written (see the
webhooks docs). No more scheduling a guess and getting zero rows.

**Pagination — two interchangeable styles:**

*Cursor (recommended):* read `pagination.nextCursor` from the response and
send it back as `?cursor=`. Keep going while `pagination.hasMore` is true;
the last page returns `hasMore: false` and `nextCursor: null`. Do not send
`offset` alongside a cursor — it is ignored. Note that `total` counts the
rows remaining from your cursor position onward, so it shrinks as you page.

*Offset:* send `limit` (default 50, max 100) and `offset`, and page until
`hasMore` is false. Here `total` is the full count for the trading day.

Accounts are ordered by daily P&L, highest first.

**Use cases:**
- Daily performance reports
- Reconciliation with your internal systems
- Compliance and risk monitoring
- Partner dashboards



## OpenAPI

````yaml /api-reference/openapi.json get /v1/organization/snapshots/accounts
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/snapshots/accounts:
    get:
      tags:
        - Reconciliation
      summary: Get end-of-day account snapshots
      description: >-
        Returns every account that traded during a CME trading day, with their
        end-of-day balances and performance.


        **Produced once per trading day**, shortly after market close.


        **What you get per account:**

        - Starting and ending balances

        - Daily P&L and total P&L

        - High water mark

        - Fill count and contracts traded

        - Status changes and violation reasons


        **CME trading day:** 17:00 CT previous day → 16:00 CT current day.


        **Server-side account scoping:**

        Pass `?accountId=<uuid>` or `?accountId=<uuid>,<uuid>,...` (up to 100)
        to

        retrieve snapshots for exactly the accounts you care about — no need to
        pull

        the whole org and filter locally. Useful for multi-tenant setups where
        each

        tenant maps to a subset of accounts. IDs outside your organization
        return

        `404 ACCOUNT_NOT_FOUND`, so the scoping is safe by construction.


        **Knowing when snapshots are ready:**

        The response includes `latestCompletedTradingDay` — the most recent
        trading

        day for which EOD snapshots exist for your organization. Poll it, or
        better:

        subscribe to the `snapshot.ready` webhook event, which fires once per

        organization per trading day the moment the EOD batch is written (see
        the

        webhooks docs). No more scheduling a guess and getting zero rows.


        **Pagination — two interchangeable styles:**


        *Cursor (recommended):* read `pagination.nextCursor` from the response
        and

        send it back as `?cursor=`. Keep going while `pagination.hasMore` is
        true;

        the last page returns `hasMore: false` and `nextCursor: null`. Do not
        send

        `offset` alongside a cursor — it is ignored. Note that `total` counts
        the

        rows remaining from your cursor position onward, so it shrinks as you
        page.


        *Offset:* send `limit` (default 50, max 100) and `offset`, and page
        until

        `hasMore` is false. Here `total` is the full count for the trading day.


        Accounts are ordered by daily P&L, highest first.


        **Use cases:**

        - Daily performance reports

        - Reconciliation with your internal systems

        - Compliance and risk monitoring

        - Partner dashboards
      operationId: getV1OrganizationSnapshotsAccounts
      parameters:
        - description: CME trading day (YYYY-MM-DD). Defaults to today.
          name: tradingDay
          in: query
          required: false
          schema:
            type: string
            pattern: ^\d{4}-\d{2}-\d{2}$
        - description: Filter by account status
          name: status
          in: query
          required: false
          schema:
            type: string
            enum:
              - in_progress
              - passed
              - failed
              - not_started
              - expired
        - description: >-
            Scope results to specific accounts: one account UUID or a
            comma-separated list (max 100). Every ID must belong to your
            organization, otherwise 404 ACCOUNT_NOT_FOUND.
          name: accountId
          in: query
          required: false
          schema:
            type: string
        - description: 'Results per page (default: 50, max: 100)'
          name: limit
          in: query
          schema:
            type: integer
            minimum: 1
            maximum: 100
            default: 50
        - description: Pagination offset
          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: Account snapshots retrieved
          content:
            '*/*':
              schema:
                $ref: '#/components/schemas/Model297'
        '401':
          description: Authentication required
          content:
            '*/*':
              schema:
                $ref: '#/components/schemas/Model9'
        '404':
          description: >-
            Not Found - one or more accountId values do not belong to your
            organization
          content:
            '*/*':
              schema:
                $ref: '#/components/schemas/Model298'
        '500':
          description: An unexpected error occurred
          content:
            '*/*':
              schema:
                $ref: '#/components/schemas/Model5'
      security:
        - X-API-Key: []
components:
  schemas:
    Model297:
      type: object
      properties:
        success:
          type: boolean
          example: true
        data:
          $ref: '#/components/schemas/Model296'
    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
    Model298:
      type: object
      properties:
        statusCode:
          type: number
          example: 404
        error:
          type: string
          example: Not Found
        message:
          type: string
          example: >-
            Account(s) not found in your organization:
            7c9e6679-7425-40de-944b-e07fc1f90ae7
        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
    Model296:
      type: object
      example:
        tradingDay: '2026-03-11'
        latestCompletedTradingDay: '2026-03-11'
        organizationId: a6fcc0ce-eb28-4f43-b256-96a3144b0d34
        organizationName: FakePropFirm
        accounts:
          - accountId: 7c9e6679-7425-40de-944b-e07fc1f90ae7
            userId: f994bc02-343c-4026-8a57-afc085eca8d5
            accountNumber: ACC-ABCD1234
            status: in_progress
            initialBalance: 50000
            startingBalance: 50250
            endingBalance: 50875
            dailyPnl: 625
            totalPnl: 875
            highWaterMark: 50900
            totalFills: 8
            totalContractsTraded: 14
            firstFillAt: '2026-03-11T14:30:01Z'
            lastFillAt: '2026-03-11T20:45:12Z'
            statusChanged: false
            previousStatus: null
            violationReason: null
        pagination:
          total: 142
          limit: 50
          offset: 0
          hasMore: true
          nextCursor: >-
            eyJkYWlseV9wbmwiOjYyNSwiaWQiOiIzZjJlNGE5MC1iMWM4LTQ3ZDMtOWE1Yi0yMmM3ZTQ0ZmNhYjEifQ
      properties:
        tradingDay:
          type: string
        latestCompletedTradingDay:
          type: string
          description: >-
            Most recent trading day with completed EOD snapshots for your
            organization (null if none yet). Use it — or the snapshot.ready
            webhook — to know when EOD data is available.
        organizationId:
          type: string
        organizationName:
          type: string
        accounts:
          $ref: '#/components/schemas/Model294'
        pagination:
          $ref: '#/components/schemas/Model295'
    Model294:
      type: array
      items:
        $ref: '#/components/schemas/Model293'
    Model295:
      type: object
      description: Pagination info
      properties:
        total:
          type: number
          description: >-
            Accounts for the trading day; when paginating by cursor, accounts
            remaining from your cursor onward
        limit:
          type: number
          description: Results per page
        offset:
          type: number
          description: Offset applied to this request — always 0 when a cursor was supplied
        hasMore:
          type: boolean
          description: Whether more results exist
        nextCursor:
          type: string
          description: >-
            Cursor for the next page. Pass as ?cursor= to get the next set of
            results. Null if no more results.
    Model293:
      type: object
      properties:
        accountId:
          type: string
        userId:
          type: string
        accountNumber:
          type: string
        status:
          type: string
        initialBalance:
          type: number
        startingBalance:
          type: number
        endingBalance:
          type: number
        dailyPnl:
          type: number
        totalPnl:
          type: number
        highWaterMark:
          type: number
        totalFills:
          type: number
        totalContractsTraded:
          type: number
        firstFillAt:
          type: string
        lastFillAt:
          type: string
        statusChanged:
          type: boolean
        previousStatus:
          type: string
        violationReason:
          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

- [Reconcile a trading day in one call](/platform-api/reconciliation/reconcile-a-trading-day-in-one-call.md)
- [Revert an account to a trading day or an instant](/platform-api/time-machine/revert-an-account-to-a-trading-day-or-an-instant.md)
- [Introduction](/introduction.md)
- [Get fills for a trading day](/platform-api/reconciliation/get-fills-for-a-trading-day.md)
- [Register a webhook endpoint](/platform-api/webhooks/register-a-webhook-endpoint.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.