---
title: "Get data corrections"
method: GET
path: "/organizations/{cin}/corrections"
tags: ["Organizations"]
---

# Get data corrections

`GET /organizations/{cin}/corrections`

## Request

- Base URL: `https://api.apino.sk/api/v1`
- URL: `https://api.apino.sk/api/v1/organizations/{cin}/corrections`
- Auth: HTTP bearer

Everything we changed about this organization's data on the way in, and
everything we found but would not change, with the register's original
text in both cases.

The register republishes what ORSR and ŽRSR hold, transcoding errors
included. We repair the defects we can prove — a decomposed diacritic
such as `Vy´roba` for `Výroba`, the `1800-01-01` placeholder date, a
non-breaking space transcoded to `?` — and report the rest rather than
guess. `applied: true` means we changed the stored value; `applied:
false` means we left it as the register published it and are telling you
what we saw.

This endpoint is the counterpart to changing values at all: nothing is
lost, and the original is always recoverable here — except for the
fields GDPR masking removes from `/detail`: a correction to a statutory
body's or stakeholder's `identifier`, or to their address below the
municipality, is not listed, since its original text is the masked value.

## Path parameters

- `cin` string, required

## Query parameters

- `country` 'SK' | 'CZ'

## Response `200`

Corrections for this organization. Empty when its record was clean.

- CorrectionsResponse
  - `cin` string, required
  - `country_code` 'SK' | 'CZ', required
  - `applied` integer, required: How many findings changed the stored value.
  - `reported` integer, required: How many were reported without being changed.
  - `corrections` Correction[], required
    - `organization_id` integer, required
    - `country_code` 'SK' | 'CZ', required
    - `kind` 'mojibake' | 'sentinel_date' | 'broken_space' | 'unrecognised_mojibake' | 'implausible_date' | 'lost_letter' | 'missing_postal_code', required: What was found. New kinds may be added, so treat an unknown value as "some other defect" rather than failing.
    - `path` string, required: Where in the record, e.g. `activities[3].description`.
    - `original` string, required: The register's own text, before anything we did.
    - `corrected` string: The value we stored. Present only when `applied` is true, and absent when the correction was to clear the field.
    - `suggested` string: What the value looks like it should be. Present only on findings we declined to apply, and never written to the record.
    - `applied` boolean, required

## Other responses

- `300`: CIN exists in both registers — call again with `?country=SK` or `?country=CZ`
- `400`: Validation error
- `401`: Missing or invalid API key
- `404`: Resource not found
- `429`: Rate limit exceeded

---

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