> ## Documentation Index
> Fetch the complete documentation index at: https://docs.ochy.io/llms.txt
> Use this file to discover all available pages before exploring further.

# List analyses for a subject

> Retrieve all analysis IDs and their statuses for a specific subject.
The subject must belong to the authenticated partner and must not be deleted.




## OpenAPI

````yaml /openapi.yaml get /analysis/subjects/{subject_id}
openapi: 3.0.1
info:
  title: Ochy Partner API
  version: 1.0.0
  description: >
    The Ochy Partner API lets you integrate running biomechanical analysis into
    your application.

    Upload a video of a runner, receive detailed biomechanical metrics, joint
    angles, running style

    classification, and frame-by-frame position data.
servers:
  - url: https://partner-api.ochy-prod.com
    description: Production
security:
  - apiKey: []
paths:
  /analysis/subjects/{subject_id}:
    get:
      tags:
        - Analysis
      summary: List analyses for a subject
      description: >
        Retrieve all analysis IDs and their statuses for a specific subject.

        The subject must belong to the authenticated partner and must not be
        deleted.
      operationId: getSubjectAnalyses
      parameters:
        - name: subject_id
          in: path
          required: true
          description: Subject ID.
          schema:
            type: string
          example: 550e8400-e29b-41d4-a716-446655440000
      responses:
        '200':
          description: List of analysis IDs for the subject.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/SubjectAnalysesResponse'
              example:
                analysis_ids:
                  - id: 3dde3402-94d7-462e-a784-9306207108dd
                    status: success
                  - id: 3ea20fb3-e918-4d98-94ca-7477cedae9ed
                    status: success
                  - id: 6af9c095-01c6-45d0-a290-26d9080df622
                    status: analyzing
                count: 3
        '401':
          description: Missing API key.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/AuthErrorResponse'
        '403':
          description: Invalid API key.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/AuthErrorResponse'
        '404':
          description: Subject not found.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
              example:
                detail: Subject not found
        '500':
          description: Internal server error.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
components:
  schemas:
    SubjectAnalysesResponse:
      type: object
      properties:
        analysis_ids:
          type: array
          items:
            type: object
            properties:
              id:
                type: string
                example: 3dde3402-94d7-462e-a784-9306207108dd
              status:
                type: string
                enum:
                  - pending
                  - analyzing
                  - success
                  - failed
                example: success
        count:
          type: integer
          example: 3
    AuthErrorResponse:
      type: object
      properties:
        detail:
          type: string
          example: API Key is missing
    ErrorResponse:
      type: object
      properties:
        detail:
          type: string
          example: Internal server error
        code:
          type: string
          description: Machine-readable error code (present on some errors).
          example: insufficient_credits
  securitySchemes:
    apiKey:
      type: apiKey
      in: query
      name: apiKey
      description: Your API key, passed as a query parameter on every request.

````