---
title: "Standard Fixes"
method: POST
path: "/v1/fix-standard"
tags: ["fixer", "PUBLIC"]
---

# Standard Fixes

`POST /v1/fix-standard`

Standard fixes endpoint - applies non-parsing fixes. Phase 2 of the 3-phase architecture. Takes the output from Phase 1 (detection) and applies CSS, UI, dependency, and type fixes. The output can be used as input to Phase 3 (AI fallback).

## Request body

- object
  - `files` object[], required — List of files to fix (can be output from step 1)
    - `path` string, required — Path to the file
    - `contents` string, required — File contents
  - `remaining_diagnostics` object, required — Diagnostics to fix (output from step 1 or previous fixes)
    - `file_to_diagnostics` object — Diagnostics grouped by file
  - `fix_types` string[] — Types of standard fixes to apply
  - `template_path` string — Template path for project context
  - `event_id` string — Unique identifier for tracking
  - `continuation_event_id` string — Event ID from Step 1 to continue with the same temp directory
  - `mode` 'project' | 'files' — Fixer mode: 'project' for full analysis, 'files' for incremental
  - `bundle` boolean — Whether to bundle the project after fixes
  - `meta` object, nullable — Meta information for the request
    - `external_id` string, nullable — Customer tracking identifier

## Response `200`

Successful standard fix response

- object
  - `data` object, required — The actual response data
    - `success` boolean, required — Whether fixes were successfully applied
    - `files_fixed` number, required — Number of files that were fixed
    - `issues_resolved` number, required — Number of issues resolved
    - `issues_remaining` number, required — Number of issues still remaining
    - `execution_time` number, required — Total execution time in seconds
    - `changed_files` object[], required — Files that were modified during fixing
      - `path` string, required — Path of the file
      - `contents` string, required — Contents of the file
    - `remaining_diagnostics` object, required — Remaining diagnostics after standard fixes
      - `file_to_diagnostics` object — Diagnostics grouped by file
    - `bundled_files` object[], nullable — Bundled output files if bundling was requested
      - `path` string, required — Path of the file
      - `contents` string, required — Contents of the file
    - `fix_types_applied` string[], required — Types of fixes that were actually applied
  - `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)