---
title: "Submit a merchant match correction"
method: POST
path: "/v1/corrections"
tags: ["Flywheel"]
---

# Submit a merchant match correction

`POST /v1/corrections`

## Request

- Base URL: `https://api.nashboard.ai`
- URL: `https://api.nashboard.ai/v1/corrections`
- Auth: one of:
  - HTTP bearer
  - API key in header `X-API-Key`

Required scope: `corrections:write`. Report that a returned merchant match was wrong. Corrections feed the HUMAN-CONFIRMED learning corpus used by the disambiguation cron. Idempotent via optional X-Idempotency-Key header.

## Headers

- `X-Nashboard-Version` '2026-06-13'
- `X-Idempotency-Key` string

## Request body

- CorrectionRequest: At least one of corrected_merchant_id or correction_reason is required.
  - `enrich_request_id` string, uuid
  - `receipt_id` string, uuid
  - `transaction_id` string, uuid
  - `predicted_merchant_id` string, uuid
  - `corrected_merchant_id` string, uuid
  - `correction_reason` string

## Response `201`

Correction recorded.

- object
  - `id` string, uuid, required

## Other responses

- `400`: Bad request (invalid JSON, invalid ID, invalid cursor, etc.)
- `401`: Missing, malformed, or invalid API key.
- `403`: Insufficient scope or scope escalation attempt.
- `404`: Resource not found.
- `409`: Conflict (e.g. email already taken).
- `413`: Request body too large.
- `415`: Unsupported media type.
- `422`: Request body failed schema validation.
- `429`: Rate limited, quota exceeded, or DP budget exhausted.
- `500`: Internal server error.
- `502`: Upstream dependency error (e.g. receipt image storage unavailable — code storage_failure).

---

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