> ## Documentation Index
> Fetch the complete documentation index at: https://docs.immoteur.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Report an issue through the API

> Choose an issue report, copy an example, replace its IDs, and submit it to POST /issues

Choose the problem you found, copy the matching request from the API reference, replace the IDs, and send it to `POST /issues`.

The API records your report; it does not change a `Property`, a `Classified`, a listing status, or a grouping.

## Choose a report and example

<Tabs>
  <Tab title="Data">
    ```mermaid theme={null}
    flowchart TD
      accTitle: Choose a data report
      accDescr: Use a data report when information on one Property or one Classified listing is wrong.
      A[Wrong information] --> B{Where is it?}
      B -->|Property| C[Property data]
      B -->|Classified listing| D[Classified data]
    ```
  </Tab>

  <Tab title="Status">
    ```mermaid theme={null}
    flowchart TD
      accTitle: Choose a status report
      accDescr: Use a status report when one or more Classified listings have an incorrect status.
      A[Incorrect listing status] --> B[Classified status]
    ```
  </Tab>

  <Tab title="Grouping">
    ```mermaid theme={null}
    flowchart TD
      accTitle: Choose a grouping report
      accDescr: Use a grouping report when records should be merged or separated.
      A[Incorrect grouping] --> B{What should happen?}
      B -->|Join records| C[Merge]
      B -->|Separate listings| D[Split]
    ```
  </Tab>

  <Tab title="Other">
    ```mermaid theme={null}
    flowchart TD
      accTitle: Choose another issue report
      accDescr: Use an other report for a problem on one Property or Classified listing that is not covered by data, status, or grouping reports.
      A[Another problem] --> B{Where is it?}
      B -->|Property| C[Other Property]
      B -->|Classified listing| D[Other Classified]
    ```
  </Tab>
</Tabs>

A `Property` is the real-estate asset that Immoteur groups from listings. A `Classified` is one source listing for that property.

| If you found                                                            | Use          |
| ----------------------------------------------------------------------- | ------------ |
| Incorrect information on one property or listing, including status data | `data`       |
| An incorrect status on one or more listings                             | `status`     |
| Properties or listings that should be grouped or separated              | `clustering` |
| Another problem on one property or listing                              | `other`      |

Open [Create an issue report](/api-reference/issue/create-an-issue-report) and copy the matching example. The endpoint has seven named examples.

For `data` and `other`, choose the Property or Classified example that matches the problem; its `targetType` records that choice.

## Replace the IDs and check the selection

Replace every synthetic UUID with an ID that your credentials can access. Use only the fields in the selected example: do not add fields from another example or send `null`.

For `data`, choose the Property or Classified example for the affected resource, set its one `propertyId` or `classifiedId`, and select the `issueFacets` that describe the problem. `status` is available as a data facet.

For `status`, send `classifiedIds` and an `expectedStatus` that differs from the current status of every selected listing. The report is rejected if any selected listing already has that status or cannot be used.

For `merge`, send `propertyIds`, `classifiedIds`, or both, and select at least two current properties in total. Selecting a `Property` includes its current listings; selecting a `Classified` includes only that listing. An overlap stays in the report as evidence.

For a merge or split, each supplied ID list has 1–100 IDs.

For `split`, provide the source `propertyId` and the listings to separate. Every selected `Classified` must still belong to that property.

Add a `comment` of up to 4,000 characters when it helps explain a data, status, or grouping problem. An `other` report requires a nonblank `comment`.

## Submit or fix the report

Send the completed request to `POST /issues`. A `201` response returns the receipt for the stored report; it does not correct the data, status, or grouping.

A `422` response means the request fields or selected resources no longer meet the requirements. Read the response, refresh the affected records, and rebuild the request from the matching [API reference example](/api-reference/issue/create-an-issue-report).

For a status report, check every listing against `expectedStatus`. For a merge, confirm that the selection still covers at least two properties; for a split, confirm every listing still belongs to the source property.