> ## 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.

# Read one trader's risk findings with their proof

> Every finding of the daily risk reports that names the trader, newest first, each with its level, the reasons in words, the rule that fired with the values observed, the other traders involved, and the evidence: both positions with entry, exit, size and profit per side and the seconds they overlapped; for a shared device or address, who used it, when, and how long their sessions overlapped. `coverage` says which trading days are included and which failed or are still to come. At most 500 findings (`truncated`). `stake` is the money at stake with the trader, as on their inbox row.

```bash
curl "https://api.hyperprop.com/platform/v1/organization/risk/traders/2b1f0c9e-4d3a-4e5f-8a7b-6c5d4e3f2a1b/findings?days=30" \
  -H "X-API-Key: hp_live_your_key_here"
```

**Permissions:** requires **view** access to "Traders & accounts". Full sign-in addresses and device ids need "Risk investigations"; without it they are shortened.

**Access:** read-only and full-access API keys. Dashboard members need view access to Traders & accounts.



## OpenAPI

````yaml https://api.hyperprop.com/platform/openapi.json get /v1/organization/risk/traders/{traderId}/findings
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: Instruments
    description: >-
      The contracts your organization's accounts can trade, with their
      specifications.
  - 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: Mass credit
    description: >-
      Credit back losses across many accounts after an incident, as background
      jobs you can follow, pause, export and reverse.
  - name: Webhooks
    description: Register webhook endpoints and inspect deliveries.
  - name: Events
    description: Your organization's event history, to replay or audit what happened.
  - name: Real-time streams
    description: >-
      Live events and trading data over a WebSocket, for dashboards and CRMs
      that update as things happen.
  - name: Reconciliation
    description: Balances, end-of-day snapshots, and fills for reconciliation.
  - name: Analytics
    description: Organization performance, revenue and top traders.
  - name: Risk
    description: Firm profit and loss and plan economics.
  - name: Trader insights
    description: >-
      What your traders hold right now and over time, your top traders, and the
      traders you follow.
  - name: Billing and invoices
    description: >-
      Your Hyperprop invoices, credits and billing details, with usage so far
      this month, billing cycles, forecasts and CSV exports.
  - name: Team and roles
    description: Manage dashboard access for your staff.
  - name: API keys
    description: >-
      Manage your organization's API keys: rotation, read-only keys and IP
      allowlists.
  - name: Logs and health
    description: >-
      API request logs, the audit log, integration health, and idempotency key
      recovery.
  - 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/risk/traders/{traderId}/findings:
    get:
      tags:
        - Risk
      summary: Read one trader's risk findings with their proof
      description: >-
        Every finding of the daily risk reports that names the trader, newest
        first, each with its level, the reasons in words, the rule that fired
        with the values observed, the other traders involved, and the evidence:
        both positions with entry, exit, size and profit per side and the
        seconds they overlapped; for a shared device or address, who used it,
        when, and how long their sessions overlapped. `coverage` says which
        trading days are included and which failed or are still to come. At most
        500 findings (`truncated`). `stake` is the money at stake with the
        trader, as on their inbox row.


        ```bash

        curl
        "https://api.hyperprop.com/platform/v1/organization/risk/traders/2b1f0c9e-4d3a-4e5f-8a7b-6c5d4e3f2a1b/findings?days=30"
        \
          -H "X-API-Key: hp_live_your_key_here"
        ```


        **Permissions:** requires **view** access to "Traders & accounts". Full
        sign-in addresses and device ids need "Risk investigations"; without it
        they are shortened.


        **Access:** read-only and full-access API keys. Dashboard members need
        view access to Traders & accounts.
      operationId: getV1OrganizationRiskTradersTraderidFindings
      parameters:
        - description: '`traderId` from the inbox'
          name: traderId
          in: path
          required: true
          example: 2b1f0c9e-4d3a-4e5f-8a7b-6c5d4e3f2a1b
          schema:
            type: string
            maxLength: 64
        - description: Trading days to include, 1 to 90
          name: days
          in: query
          schema:
            type: integer
            minimum: 1
            maximum: 90
            default: 30
        - description: Lowest finding level to include
          name: minLevel
          in: query
          example: medium
          schema:
            type: string
            enum:
              - low
              - medium
              - high
            default: low
        - name: If-None-Match
          in: header
          required: false
          description: >-
            Optional. The `ETag` of the answer you already have. When the answer
            would be the same, the response is `304` without a body.
          example: '"Hq3mB1c0s8n2JkVbQy4Tz9uXw5E"'
          schema:
            type: string
      responses:
        '200':
          description: The trader's findings
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Model1255'
        '304':
          description: >-
            Not modified: the answer is the same as the one whose `ETag` you
            sent in `If-None-Match`. No body; keep using the answer you have.
        '400':
          description: Invalid request data
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Model351'
        '401':
          description: Authentication required
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Model15'
        '403':
          description: This API key does not have admin permissions
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Model511'
        '404':
          description: Not found
        '500':
          description: Internal error (`RISK_FINDINGS_ERROR`)
        '503':
          description: Not available yet (`RISK_REPORTS_UNAVAILABLE`)
        '504':
          description: >-
            Gateway Timeout - The request did not complete within 25 seconds
            (`REQUEST_TIMEOUT`). Nothing was changed; retry, or narrow the
            request (for example a shorter date range).
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Model1256'
      security:
        - X-API-Key: []
components:
  schemas:
    Model1255:
      type: object
      properties:
        success:
          type: boolean
          example: true
        data:
          $ref: '#/components/schemas/Model1254'
    Model351:
      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 request data
        code:
          type: string
          description: Machine-readable error code — switch on this, not on message text
          example: BAD_REQUEST
    Model15:
      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
    Model511:
      type: object
      properties:
        success:
          type: boolean
          description: Always false on errors
          example: false
        statusCode:
          type: number
          example: 403
        error:
          type: string
          example: Forbidden
        message:
          type: string
          example: This API key does not have admin permissions
        code:
          type: string
          description: Machine-readable error code — switch on this, not on message text
          example: INSUFFICIENT_PERMISSIONS
    Model1256:
      type: object
      properties:
        statusCode:
          type: number
          example: 504
        error:
          type: string
          example: Gateway Timeout
        message:
          type: string
          example: >-
            The request did not complete within 25 seconds. Try again, or narrow
            it (for example a shorter date range).
        code:
          type: string
          description: Machine-readable error code — switch on this, not on message text
          example: REQUEST_TIMEOUT
    Model1254:
      type: object
      properties:
        organizationId:
          type: string
          x-format:
            guid: true
        traderId:
          type: string
          example: 2b1f0c9e-4d3a-4e5f-8a7b-6c5d4e3f2a1b
        traderName:
          type: string
        accounts:
          $ref: '#/components/schemas/Model1251'
        coverage:
          $ref: '#/components/schemas/coverage'
        review:
          $ref: '#/components/schemas/Model1252'
        findings:
          $ref: '#/components/schemas/findings'
        truncated:
          type: boolean
        stake:
          $ref: '#/components/schemas/Model1253'
    Model1251:
      type: array
      items:
        $ref: '#/components/schemas/Model1250'
    coverage:
      type: object
      description: >-
        Which trading days the list covers; show "no findings" only when
        `complete` is true
      properties:
        from:
          type: string
          example: '2026-11-06'
        to:
          type: string
          example: '2026-11-12'
        complete:
          type: boolean
          description: >-
            True only when every closed trading day in the range has all its
            reports
          example: false
        days:
          $ref: '#/components/schemas/days'
        failedDays:
          type: integer
          example: 1
        pendingDays:
          type: integer
          example: 0
        truncatedDays:
          type: integer
          example: 0
        missingDays:
          type: integer
          example: 0
    Model1252:
      type: object
      properties:
        state:
          type: string
        outcome:
          type: string
        reason:
          type: string
        note:
          type: string
        updatedAt:
          type: string
    findings:
      type: array
      items:
        $ref: '#/components/schemas/finding'
    Model1253:
      type: object
      description: >-
        Money at stake with the trader, as on the inbox row; null when it could
        not be read in time
      properties:
        payableProfit:
          type: number
          example: 12400.5
        fundedAccounts:
          type: integer
          example: 2
        paidBeforeReview:
          type: number
          example: 850
        payoutPending:
          type: string
    Model1250:
      type: object
    days:
      type: array
      description: >-
        Closed trading days, newest first. The open day is not listed, nor
        Saturday and Sunday (no session) unless something was stored for them.
        There is no holiday calendar: holidays are computed like any weekday
      items:
        $ref: '#/components/schemas/Model624'
    finding:
      type: object
      properties:
        findingId:
          type: string
          example: 5f0e8a1c-3b2d-5c4e-9f6a-7b8c9d0e1f2a
          x-format:
            guid: true
        report:
          $ref: '#/components/schemas/Model1021'
        tradingDay:
          type: string
          example: '2026-11-12'
        level:
          $ref: '#/components/schemas/Model1022'
        flags:
          type: boolean
          description: Whether the finding puts its traders in the inbox
          example: true
        reasons:
          $ref: '#/components/schemas/Model1024'
        summary:
          type: string
          example: Opposite NQ positions with another trader for 412 s
        rule:
          $ref: '#/components/schemas/rule'
        traderIds:
          $ref: '#/components/schemas/Model1025'
        otherTraders:
          $ref: '#/components/schemas/otherTraders'
        pnl:
          type: number
          example: 260.5
        evidence:
          $ref: '#/components/schemas/evidence'
        redacted:
          type: boolean
          description: >-
            Addresses and device ids are shortened: the role lacks Risk
            investigations
          example: false
        supersededAt:
          type: string
          description: >-
            Present when a later computation of the day replaced this finding;
            kept because a review decision names it
          x-format:
            isoDate: true
    Model624:
      type: object
      properties:
        tradingDay:
          type: string
          example: '2026-11-11'
        state:
          $ref: '#/components/schemas/Model623'
        expectedAt:
          type: string
          description: >-
            Pending days only: when the nightly run is due (Sunday's day: Monday
            17:10 Chicago)
          example: '2026-11-16T23:10:00.000Z'
          x-format:
            isoDate: true
        reports:
          $ref: '#/components/schemas/reports'
        truncated:
          $ref: '#/components/schemas/truncated'
    Model1021:
      type: string
      example: hedge_pairs
      enum:
        - hedge_pairs
        - self_hedges
        - copy_pairs
        - copy_groups
        - shared_devices
        - news_window_fills
    Model1022:
      type: string
      description: Null for days stored before levels existed
      example: high
      enum:
        - low
        - medium
        - high
    Model1024:
      type: array
      items:
        $ref: '#/components/schemas/Model1023'
    rule:
      type: object
      description: The rule that fired and the values observed
      properties:
        name:
          type: string
        observed:
          $ref: '#/components/schemas/observed'
    Model1025:
      type: array
      items:
        type: string
    otherTraders:
      type: array
      items:
        $ref: '#/components/schemas/Model1026'
    evidence:
      type: object
      description: >-
        The stored finding: positions, times, sizes and profit per side; for a
        shared device or address its traders and overlaps
    Model623:
      type: string
      description: >-
        `pending`: the nightly run for the day is not due yet or ran less than
        12 hours ago; `missing`: still nothing 12 hours after it was due
      example: failed
      enum:
        - ready
        - partial
        - failed
        - truncated
        - pending
        - missing
    reports:
      type: object
      description: Per report, when not all are ready
    truncated:
      type: array
      description: Reports cut at their row limit
      items:
        type: string
    Model1023:
      type: object
      properties:
        code:
          type: string
          example: repeat_days
        text:
          type: string
          example: Also seen on 2 other days of the last 30
    observed:
      type: object
    Model1026:
      type: object
      properties:
        traderId:
          type: string
        traderName:
          type: string
  securitySchemes:
    X-API-Key:
      type: apiKey
      name: X-API-Key
      in: header
      description: >-
        Organization API key (`hp_live_...`), sent in the `X-API-Key` header.
        Create, rotate and restrict keys in the dashboard or with the API keys
        endpoints; an organization can have two active keys, so you can rotate
        without downtime. A **full-access** key can call every endpoint in this
        reference. A **read-only** key can call `GET` endpoints (and create a
        trading stream token); any other request returns `403 READ_ONLY_KEY`. A
        key with an IP allowlist returns `403 IP_NOT_ALLOWED` from any other
        address. Each endpoint lists which keys can call it under **Access**.

````

## Related topics

- [Read one risk finding with its proof](https://docs.hyperprop.com/platform-api/risk/read-one-risk-finding-with-its-proof.md)
- [Read the daily risk report of a trading day](https://docs.hyperprop.com/platform-api/risk/read-the-daily-risk-report-of-a-trading-day.md)
- [Read the risk money summary](https://docs.hyperprop.com/platform-api/risk/read-the-risk-money-summary.md)
- [List stored trading patterns](https://docs.hyperprop.com/platform-api/risk/list-stored-trading-patterns.md)
- [List daily risk reports](https://docs.hyperprop.com/platform-api/risk/list-daily-risk-reports.md)


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