---
title: "Get what a Fix for a finding would use"
method: GET
path: "/experimental/findings-v2/{findingId}/fix"
tags: ["Findings V2"]
---

# Get what a Fix for a finding would use

`GET /experimental/findings-v2/{findingId}/fix`

## Request

- Base URL: `https://api.tessl.io`
- URL: `https://api.tessl.io/experimental/findings-v2/{findingId}/fix`
- Auth: none declared

Reports the repository and base branch a Fix would use, whether a Tessl GitHub App can write to that repository, the suggested agent instructions, the finding's newest Fix run, and, when the project's Implement Loop is active, where a ticket for the finding would be filed instead. Poll it while waiting for GitHub write access.

## Path parameters

- `findingId` string, uuid, required

## Headers

- `Authorization` string

## Response `200`

Default Response

- object
  - `links` object, required
    - `self` string, uri, required
  - `data` object, required
    - `id` string, uuid, required
    - `type` 'finding-v2-fix', required
    - `attributes` object, required
      - `repository` string, nullable, required: The finding's GitHub repository as owner/name, or null when its project is not on GitHub.
      - `baseBranch` string, nullable, required: The branch a Fix targets by default, or null when it cannot be read.
      - `githubWriteAccess` union, required: Whether a Tessl GitHub App can write to the repository. `unsupported` means the project is not on GitHub.
        - 'accessible'
        - 'denied'
        - 'inconclusive'
        - 'unsupported'
      - `suggestedInstructions` string, required
      - `latestRun` object, nullable, required: The newest Fix run for this finding, in any status.
        - `id` string, uuid, required
        - `status` union, required
          - 'pending'
          - 'completed'
          - 'failed'
          - 'cancelled'
        - `createdAt` string, date-time, required
        - `outcome` object, nullable, required: What the agent reported, or null while it has reported nothing. A run can finish with status `completed` and outcome `failed` when the agent opened no pull request; `reason` says why.
          - `status` union, required: What the skill did: `succeeded` — it did its work; `no_action` — it ran but made no change; `needs_input` — it asked a blocking question and stopped; `failed` — it tried and could not complete. Not the same as the launch run's own status, which says whether the platform got the skill to run at all.
            - 'succeeded'
            - 'no_action'
            - 'needs_input'
            - 'failed'
          - `reason` string
      - `ticketTarget` union, required: Where a ticket for this finding would be filed when the project's Implement Loop is active: the Linear team, or the GitHub repository and the label Implement starts on. Null when a Fix opens a pull request instead.
        - object
          - `source` 'linear', required
          - `team` object, required
            - `id` string, required
            - `name` string, required
        - object
          - `source` 'github', required
          - `repository` string, required: owner/name
          - `label` string, required

## Other responses

- `401`: Unauthorized
- `403`: Forbidden
- `404`: Not Found
- `500`: Internal Server Error
- `503`: Service Unavailable

## Changes

- **2026-10-21** `4f3ca2dfb0bc`: 1 info
  - added the required property `data/attributes/ticketTarget` to the response with the `200` status
- **2026-10-15** `f06a9f376235`: 1 info
  - endpoint added

[Operation history](https://skmtc.dev/tessl/apis/tessl-api/changes/experimental/findings-v2/:findingId/fix/get.md)

---

[API](https://skmtc.dev/tessl/apis/tessl-api.md) · [All operations](https://skmtc.dev/tessl/apis/tessl-api/llms.txt) · [OpenAPI document](https://skmtc.dev/tessl/apis/tessl-api/revisions/7386f1e6295b?raw)