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

# Get Run Records

> Return the rows produced/judged on a run.

Payload-md shape: `{ run_id, status, completed_at, records: [...] }`.
Each row carries query/response (from prompt_preview/response_preview),
verdict columns, blob_url, and the caller-supplied tags. Test_type and
goal are recovered from the tags map (set by the eval resolver path).

**One run, two status vocabularies.** `GET /rt/runs/{run_id}` reports the run record's status, which is lowercase (`queued`, `running`, `paused`, `completed`, `failed`, `cancelled`). `GET /rt/runs/{run_id}/results` and `GET /rt/runs/{run_id}/records` report the red-team stage's status, which is capitalised (`Queued`, `Running`, `Finished`, `Failed`). One finished run therefore answers "completed" on the first and "Finished" on the other two. They are different pieces of state that share a field name, and are deliberately not reconciled - match against the vocabulary of the endpoint you called. `status` in this payload is the capitalised form, so a finished run reads `Finished`.

This serves **red-team runs as well as evals**. On a red-team run each record carries `query`, `response`, `test_type`, `category`, `sub_category`, `success`, `response_classification` and `reasoning`.

Use this path as written. The `records_url` field on the results payload is emitted with the internal `/v1/...` spelling and returns `400` if followed verbatim - `/rt/runs/{run_id}/records` is the published address for the same resource.

**Paged.** Each call returns at most `limit` records (1-1000, default 1000) starting at `offset` (default 0), ordered by creation time. `total` is the run's full record count and `next_offset` is the `offset` to request next, or `null` on the last page - keep requesting with `offset=next_offset` until it is `null` to read every record. A `limit` or `offset` that is not a valid integer in range returns `400`.



## OpenAPI

````yaml GET /rt/runs/{run_id}/records
openapi: 3.0.0
info:
  title: Enkrypt AI APIs
  version: 2.0.0
servers:
  - url: https://api.enkryptai.com
security:
  - apiKeyAuth: []
tags:
  - name: Guardrails
  - name: Code of Conduct
  - name: Endpoints
  - name: Redteam
    description: >-
      Red Team API: submit red-team / threat-modeling / playground / eval runs,
      then poll run status, records, results and compliance. Also two-phase
      threat modeling (categories + data), dataset retrieval, model health,
      findings and risk mitigation. The previous task-based Red Team API is
      under **Archived**.
  - name: Deployments
  - name: AI Proxy
  - name: Leaderboard
  - name: Archived
  - name: MCP Hub
    description: >-
      MCP Hub vulnerability scanning APIs. Submitting scans (the POST endpoints)
      is open to all authenticated callers. The scan **retrieval** APIs — Get
      Scan Job Status, Get Complete Scan Results, List Scans, and Get MCP Hub
      Scan Statistics (the GET endpoints) — are an **enterprise data-license
      feature**: they require your organization to have MCP Hub API access
      enabled by Enkrypt, otherwise they return `403`. Contact us at
      support@enkryptai.com to enable access.
  - name: MCP Registry Servers
  - name: MCP Gateways
  - name: MCP Playground
  - name: Skill Scanner
    description: >-
      Skill Scanner APIs: submit an agent skill (a directory inside a git
      repository) for security scanning, then read the verdict, the risk level
      and the full report. Scanning is asynchronous — a scan takes roughly 30–90
      seconds, so `POST /skill-hub/scan` returns a `scan_id` you poll.


      You see your organization's scans and nobody else's. The identity comes
      from your API key, never from your request — sending `user_email` is a
      `400`.


      For an organization or project API key, scans are filed under the
      **organization**, so every member sees every scan the organization has
      run, whichever project or member submitted it. For an individual account
      it is simply your own scans. Either way List Skill Scans needs no
      parameter to say who you are.
  - name: Compliance
    description: >-
      Compliance APIs: connect a ChatGPT Enterprise workspace, then keep reading
      its compliance logs and scanning every message through one of your saved
      guardrails.


      Every endpoint here — reads as well as writes — requires the **governance
      officer** role on the project your API key belongs to. The organization
      owner is **not** exempt: an owner who has not been granted the role gets
      `403` like anyone else. An individual (non-organization) account cannot
      hold the role at all, so compliance is an organization-only feature today.


      A scan is addressed by name in the `X-Enkrypt-Scan` header, within the
      project its API key belongs to. Message text is never stored: Get
      Compliance Message fetches it live from the provider, and only while the
      provider still holds it.
paths:
  /rt/runs/{run_id}/records:
    get:
      tags:
        - Redteam
      summary: Get Run Records
      description: >-
        Return the rows produced/judged on a run.


        Payload-md shape: `{ run_id, status, completed_at, records: [...] }`.

        Each row carries query/response (from prompt_preview/response_preview),

        verdict columns, blob_url, and the caller-supplied tags. Test_type and

        goal are recovered from the tags map (set by the eval resolver path).


        **One run, two status vocabularies.** `GET /rt/runs/{run_id}` reports
        the run record's status, which is lowercase (`queued`, `running`,
        `paused`, `completed`, `failed`, `cancelled`). `GET
        /rt/runs/{run_id}/results` and `GET /rt/runs/{run_id}/records` report
        the red-team stage's status, which is capitalised (`Queued`, `Running`,
        `Finished`, `Failed`). One finished run therefore answers "completed" on
        the first and "Finished" on the other two. They are different pieces of
        state that share a field name, and are deliberately not reconciled -
        match against the vocabulary of the endpoint you called. `status` in
        this payload is the capitalised form, so a finished run reads
        `Finished`.


        This serves **red-team runs as well as evals**. On a red-team run each
        record carries `query`, `response`, `test_type`, `category`,
        `sub_category`, `success`, `response_classification` and `reasoning`.


        Use this path as written. The `records_url` field on the results payload
        is emitted with the internal `/v1/...` spelling and returns `400` if
        followed verbatim - `/rt/runs/{run_id}/records` is the published address
        for the same resource.


        **Paged.** Each call returns at most `limit` records (1-1000, default
        1000) starting at `offset` (default 0), ordered by creation time.
        `total` is the run's full record count and `next_offset` is the `offset`
        to request next, or `null` on the last page - keep requesting with
        `offset=next_offset` until it is `null` to read every record. A `limit`
        or `offset` that is not a valid integer in range returns `400`.
      operationId: get_run_records_v1_runs__run_id__records_get
      parameters:
        - name: run_id
          in: path
          required: true
          schema:
            type: string
            title: Run Id
        - name: limit
          in: query
          required: false
          description: Maximum records to return, 1-1000.
          schema:
            type: integer
            minimum: 1
            maximum: 1000
            default: 1000
            title: Limit
        - name: offset
          in: query
          required: false
          description: Number of records to skip. Use the previous page's `next_offset`.
          schema:
            type: integer
            minimum: 0
            default: 0
            title: Offset
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/RTv2RecordsReport'
        '400':
          description: Invalid `limit` or `offset`.
          content:
            application/json:
              schema:
                type: object
                properties:
                  detail:
                    type: string
                    title: Detail
        '422':
          description: Validation Error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/RTv2HTTPValidationError'
components:
  schemas:
    RTv2RecordsReport:
      properties:
        run_id:
          type: string
          title: Run Id
        status:
          type: string
          title: Status
        completed_at:
          type: string
          format: date-time
          nullable: true
          title: Completed At
        records:
          items:
            $ref: '#/components/schemas/RTv2RecordRow'
          type: array
          title: Records
        total:
          type: integer
          title: Total
          description: Total records in the run, across all pages.
        limit:
          type: integer
          title: Limit
          description: The page size applied to this response.
        offset:
          type: integer
          title: Offset
          description: The offset this page starts at.
        next_offset:
          type: integer
          nullable: true
          title: Next Offset
          description: The `offset` for the next page, or `null` on the last page.
      type: object
      required:
        - run_id
        - status
        - records
        - total
        - limit
        - offset
      title: RecordsReport
    RTv2HTTPValidationError:
      properties:
        detail:
          items:
            $ref: '#/components/schemas/RTv2ValidationError'
          type: array
          title: Detail
      type: object
      title: HTTPValidationError
    RTv2RecordRow:
      properties:
        query:
          type: string
          title: Query
        response:
          title: Response
          type: string
        test_type:
          title: Test Type
          type: string
        category:
          type: string
          nullable: true
          title: Category
        sub_category:
          type: string
          nullable: true
          title: Sub Category
        goal:
          type: string
          nullable: true
          title: Goal
        success:
          type: boolean
          nullable: true
          title: Success
        response_classification:
          type: string
          nullable: true
          title: Response Classification
        reasoning:
          type: string
          nullable: true
          title: Reasoning
        confidence:
          type: number
          nullable: true
          title: Confidence
        blob_url:
          type: string
          nullable: true
          title: Blob Url
        tags:
          additionalProperties: true
          type: object
          nullable: true
          title: Tags
      type: object
      required:
        - query
        - response
        - test_type
      title: RecordRow
    RTv2ValidationError:
      properties:
        loc:
          items:
            anyOf:
              - type: string
              - type: integer
          type: array
          title: Location
        msg:
          type: string
          title: Message
        type:
          type: string
          title: Error Type
        input:
          title: Input
        ctx:
          type: object
          title: Context
      type: object
      required:
        - loc
        - msg
        - type
      title: ValidationError
  securitySchemes:
    apiKeyAuth:
      type: apiKey
      in: header
      name: apikey

````

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