---
title: "Detect Issues"
method: POST
path: "/v1/fix-parsing-and-diagnose"
tags: ["fixer", "PUBLIC"]
---

# Detect Issues

`POST /v1/fix-parsing-and-diagnose`

Fast detection endpoint for quick diagnostic results. Phase 1 of the 3-phase architecture. Returns issues quickly (within 1-3 seconds) and provides metadata about available fixes and time estimates. Does not apply any fixes, only analyzes code.

## Request body

- object
  - `files` object[], nullable — List of files to analyze (JSON format with inline contents). For large projects, use multipart/form-data with manifest + bundle instead.
    - `path` string, required — Path to the file
    - `contents` string, required — File contents
  - `event_id` string — Unique identifier for the event
  - `template_path` string — Full path to the template
  - `meta` object, nullable — Meta information for the request
    - `external_id` string, nullable — Customer tracking identifier

## Response `200`

Successful detection response

- object
  - `data` object, required — The actual response data
    - `event_id` string, required — Event ID for tracking this operation across steps
    - `diagnostics` object, required — Diagnostics split into fixable (requested) and other (not_requested) groups
      - `requested` object, nullable — Diagnostics that match the requested fix types
        - `file_to_diagnostics` object — Diagnostics grouped by file
      - `not_requested` object, nullable — Diagnostics that do not match the requested fix types
        - `file_to_diagnostics` object — Diagnostics grouped by file
    - `total_issues` number, required — Total number of issues found
    - `fixable_issues` number, required — Number of issues that can be fixed
    - `fix_types_available` object[], required — Available fix types with metadata
      - `fix_type` string, required — The type of fix available
      - `issue_count` number, required — Number of issues that can be fixed with this type
      - `estimated_time_seconds` number, required — Estimated time to fix in seconds
      - `priority` number, required — Priority of this fix type (lower is higher priority)
    - `estimated_total_fix_time` number, required — Estimated total time to fix all issues in seconds
    - `detection_time` number, required — Time taken to detect issues in seconds
    - `files_analyzed` number, required — Number of files that were analyzed
    - `fixes_applied` number, required — Number of fixes that were applied during detection
    - `diagnosis_iterations` number, required — Number of diagnostic iterations performed
    - `changed_files` object[], required — Files that were changed during detection
      - `path` string, required — Path of the file
      - `contents` string, required — Contents of the file
    - `fixer_version` string — Version of the fixer
  - `meta` object — Meta information
    - `trace_id` string, nullable — Unique trace identifier for the request
    - `external_id` string, nullable — Customer tracking identifier
  - `error` object, nullable — The error from the API query
    - `code` string, required — The error code
    - `message` string, required — The error message
    - `details` object — Details about what caused the error

## Other responses

- `400` — Invalid request
- `401` — Unauthorized
- `500` — Server error

---

[API](https://skmtc.net/benchify/apis/benchify-api.md) · [All operations](https://skmtc.net/benchify/apis/benchify-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/benchify/benchify-api/versions/1a65aea8dd7d/schema)