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

# Signaler un problème sur une advert

> Signalement gratuit d'un problème sur une annonce, avec revérification en tâche de fond.

`POST /v2/protected/adverts/{flxId}/report` sert à nous dire ce qui ne va pas sur une annonce : prix faux, annonce toujours en ligne alors que nous la disons hors ligne, doublon, mauvaise agence… L'appel est **gratuit (0 crédit)**, répond **200 immédiatement** et déclenche une revérification de l'annonce contre son portail en tâche de fond.

Le contrat exact est documenté plus bas par le bloc OpenAPI (`POST /v2/protected/adverts/{flxId}/report`).

<Warning>
  La donnée rafraîchie **n'est pas dans la réponse**. Relisez l'annonce quelques minutes plus tard avec [`GET /v2/protected/adverts/{flxId}`](/api-v2-reference/adverts/get-adverts-byt-their-flx_id), ou recevez-la sur votre [webhook d'alerte](/concepts/webhooks) si vous êtes abonné à une alerte qui la couvre.
</Warning>

<Tip>
  L'annonce est revérifiée **même si Fluximmo la croit hors ligne** — c'est exactement le cas `STILL_ONLINE`. Il n'y a **aucun cooldown** : chaque appel relance une vérification, sauf si le plafond de collectes simultanées est déjà atteint (voir `skipped_count`).
</Tip>

## Cas d'usage

* **Annonce fantôme côté Fluximmo** — vos utilisateurs voient l'annonce sur le portail alors que nous la donnons hors ligne : `STILL_ONLINE`.
* **Annonce déjà retirée** — vous constatez une 404 sur le portail alors que nous la donnons en ligne : `NOT_ONLINE_ANYMORE`.
* **Contrôle qualité de vos données** — un prix ou une surface incohérente détectée par vos règles métier : `WRONG_DATA`.
* **Dédoublonnage** — vous retrouvez le même bien sous un autre `flx_id` : `DUPLICATE`.

## Choisir le motif

`reason` est obligatoire et prend l'une de ces 7 valeurs :

* **`STILL_ONLINE`** — nous la disons hors ligne, elle est visible sur le portail.
* **`NOT_ONLINE_ANYMORE`** — nous la disons en ligne, elle a disparu du portail.
* **`WRONG_DATA`** — prix, surface ou nombre de pièces faux.
* **`WRONG_LOCATION`** — géolocalisation ou adresse fausse.
* **`DUPLICATE`** — doublon déjà présent sous un autre `flx_id`.
* **`WRONG_AGENCY`** — pro/particulier ou agence mal attribué.
* **`OTHER`** — autre cas.

`comment` est optionnel (1000 caractères maximum), mais **obligatoire quand `reason` vaut `OTHER`**. Les espaces de début et de fin sont retirés : un commentaire fait uniquement d'espaces est refusé. Les clés inconnues envoyées dans le corps sont silencieusement ignorées.

<Note>
  **Le motif détermine la profondeur de la revérification.** `STILL_ONLINE` et `NOT_ONLINE_ANYMORE` portent sur la disponibilité : ils déclenchent un contrôle léger qui met à jour le statut en ligne — le même que [`/check`](/api-v2-reference/adverts/request-an-on-demand-check-of-an-advert). Les cinq autres motifs portent sur le contenu de l'annonce : ils déclenchent une **réextraction complète**, seule capable de corriger un prix, une surface, une adresse ou une agence. Choisir le motif juste n'est donc pas cosmétique.
</Note>

## Exemples

### 1 — Annonce encore en ligne sur le portail

```bash theme={null}
curl -X POST https://api.fluximmo.io/v2/protected/adverts/123456789/report \
  -H "x-api-key: $FLUXIMMO_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "reason": "STILL_ONLINE", "comment": "Toujours visible sur leboncoin ce matin" }'
```

Réponse `200` :

```json theme={null}
{"data":{"status":"accepted","entity":"advert","flx_id":"123456789","triggered":["123456789"],"triggered_count":1,"skipped_count":0,"message":"1 advert(s) queued for an on-demand re-check."}}
```

`status` vaut `accepted` ou `nothing_to_check`. `triggered` liste les `flx_id` confiés au scraper. Sur une annonce, `skipped_count` ne peut valoir que `0` ou `1` : il passe à `1` lorsque la revérification n'a pas pu être lancée, et `status` vaut alors `nothing_to_check`. Une rafale d'appels rapprochés rend ce cas plus probable — espacez-les et réessayez. Le plafond de 10 annonces et le cas « url source absente » ne concernent que les properties.

### 2 — Motif `OTHER` : le commentaire devient obligatoire

```bash theme={null}
curl -X POST https://api.fluximmo.io/v2/protected/adverts/123456789/report \
  -H "x-api-key: $FLUXIMMO_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "reason": "OTHER" }'
```

Réponse `422` — un seul message est renvoyé par appel :

```json theme={null}
{"error":{"message":"comment is required when reason is OTHER","code":10002}}
```

## Erreurs spécifiques

Les réponses en succès sont enveloppées dans `{ "data": … }`, les erreurs dans `{ "error": { "message", "code" } }`.

* **404** — `flx_id` inconnu : `{"error":{"message":"Advert with flx_id 123456789 not found","code":10003}}`.
* **422 (validation, code `10002`)** — corps invalide, par exemple un `reason` hors énumération : `"reason must be one of the following values: STILL_ONLINE, NOT_ONLINE_ANYMORE, WRONG_DATA, WRONG_LOCATION, DUPLICATE, WRONG_AGENCY, OTHER"`. Notez le **422**, pas un 400. Un seul message est renvoyé par appel même si plusieurs champs sont invalides : branchez votre logique sur le **code**, pas sur le libellé.
* **422 (code `10003`)** — l'annonce n'a pas d'url source exploitable : `"Advert with flx_id 123456789 has no source url: it cannot be re-checked."` Le signalement ne peut pas être traité.

Détail des codes : [Codes d'erreur](/ressources/codes-erreur).

## Liens utiles

* [Récupérer une advert par flxId](/api-v2-reference/adverts/get-adverts-byt-their-flx_id) — relire la donnée rafraîchie quelques minutes plus tard.
* [Revérifier une advert](/api-v2-reference/adverts/request-an-on-demand-check-of-an-advert) — même mécanique de revérification, sans diagnostic et facturée 1 crédit.
* [Webhooks](/concepts/webhooks) — recevoir la mise à jour sans repoller.
* [Property vs Advert](/concepts/property-vs-advert) — l'équivalent existe sur les properties : [`POST /v2/protected/properties/{flxId}/report`](/api-v2-reference/properties/report-an-issue-on-a-property).
* [Bonnes pratiques](/ressources/bonnes-pratiques)

<Card title="Clé test gratuite — 1 semaine" icon="key" href="https://my.fluximmo.io">
  Créez un compte sur **my.fluximmo.io** pour récupérer une clé API test gratuite (1 semaine, accès limité). Aucun paiement requis.
</Card>


## OpenAPI

````yaml post /v2/protected/adverts/{flxId}/report
openapi: 3.0.0
info:
  title: Real-estate data API - Fluximmo V2
  description: >+
    ## Fluximmo

    ##### Real-time real estate data: Power workflows, business applications and
    decision-making.


    Real estate expert since 2017, Fluximmo aggregates, exploits, enriches &
    analyzes the 


    real-estate market in real time to offer data flows, APIs and innovative
    services to real estate professionals.


    ## Authentification

    You'll need to be authenticated with an active subscription to access our
    REST endpoints.


    To get an API-KEY please contact us at contact@fluximmo.com or book a call
    with our team: https://calendly.com/fluximmo/meet-fluximmo

    ##### How to use your API KEY

    Simply add to your HTTP request your API KEY in the headers:
    `{'x_api_key':'randomApiKey'}`


    ## Properties and Adverts

    Real-estate market can be conceptualized in different ways. We offer two
    different conceptualization depending on your needs: Properties & Adverts.

    #### Properties (BAAS)

    A property is a real-estate habitation/land/commercial/building to which is
    attached adverts.


    We gather all the adverts offering (selling or renting) this real-estate
    asset and consolidate all the information into one Property.


    A Property is by definition `de-duplicated` and can gather 1 to x adverts:
    these adverts are either duplicates from different portals or with mandates
    from different agencies or republication of the same advertising with a
    price update or not.


    The concept of property is in constant mutation until the real-estate asset
    is sold: We'll keep merging new adverts within the Property concept and
    update the price if needed.


    By it's nature in constant mutation, we do not offer the possibility to
    receive these Properties on webhooks. You'll need to use our APIs as a
    Backend As A Service (BaaS).


    #### Adverts (BAAS and WEBHOOK)

    Adverts are advertising of a real-estate property. Adverts can come from
    many sources: Agencies websites, Aggregation real-estate portals,
    Social-Networks, NewsPaper etc...


    After gathering all these adverts our proprietary AI algorithms will
    de-duplicate these adverts and associate them to a Property


    An advert have a unique URL. Meaning that the same advertising re-published
    twice (with our without any change, on the same website or not, by the same
    agency or not) is considered as 2 ads.


    You can choose either to retrieve all the Adverts or only the non duplicated
    ones. Adverts can be retrieved either by API (Search or Alerts) or Webhook

    ## Webhooks

    We offer the possibility to receive our real-estate Adverts data in
    real-time using webhooks. As soon as we gather the data, you'll receive it
    few moments later.


    Using ALERTS, you can receive new adverts matching your criteria on a
    webhook.


    ##### Webhook differences between Adverts and Properties

    As Properties are by nature in perpetual evolutions (new duplicated ads will
    be merged, new data to be consolidated etc..), we do not offer the
    possibility to receive through Webhooks the full body of the properties.
    Properties webhook will only send you the list of the properties FlxIds
    matching your search.


    You'll find below the schema of the data you would receive on your webhook
    (`/v2/sample/webhook/properties`, `/v2/sample/webhook/adverts`)

    ##### What is a webhook

    A webhook can be thought of as a type of API that is driven by events rather
    than requests


    .Instead of one application making a request to another to receive a
    response, a webhook is a service that allows one program to send data to
    another as soon as a particular event takes place.


    Webhooks are sometimes referred to as “reverse APIs,” because communication
    is initiated by the application sending the data rather than the one
    receiving it.


    With web services becoming increasingly interconnected, webhooks are seeing
    more action as a lightweight solution for enabling real-time notifications
    and data updates without the need to develop a full-scale API.

    ##### When to use a webhook instead of the REST API

    You're supposed to receive a high volume of data (frequently or not), you're
    looking for real-time data, you just have to relax and wait (no cron, no
    call on our API etc..)

    ##### Webhook implementation examples

    A webhook is simply a POST endpoint we can request

    * Python:
    https://gist.github.com/aloysius-tim/293772256526efa20d5c625c6ace036a

    * Node:
    https://gist.github.com/aloysius-tim/ea1d9feb2c527b5b09ffc356b662d14b

  version: 2.0.0
  contact: {}
  x-logo:
    url: https://www.fluximmo.com/assets/images/logo_text.png
    backgroundColor: '#F31051'
    altText: Fluximmo logo
servers:
  - url: https://api.fluximmo.io
security: []
tags:
  - name: PropertyModel
    description: <SchemaDefinition schemaRef="#/components/schemas/PropertyDto" />
  - name: AdvertModel
    description: <SchemaDefinition schemaRef="#/components/schemas/AdvertDto" />
paths:
  /v2/protected/adverts/{flxId}/report:
    post:
      tags:
        - Adverts
      summary: Report an issue on an advert
      description: >-
        Report a problem on an advert (wrong data, still online, duplicate...).
        Free. Answers 200 immediately and re-checks the advert against its
        portal in the background: read the refreshed document a couple of
        minutes later with GET /v2/protected/adverts/{flxId}, or receive it on
        your alert webhook.
      operationId: AdvertsController_reportAdvertIssue
      parameters:
        - name: flxId
          required: true
          in: path
          schema:
            type: string
      requestBody:
        required: true
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/ReportIssuePayloadDto'
      responses:
        '200':
          description: ''
          content:
            application/json:
              schema:
                properties:
                  data:
                    $ref: '#/components/schemas/RecheckResponseDto'
        '400':
          description: ''
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ExceptionDto'
        '401':
          description: ''
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ExceptionDto'
        '404':
          description: ''
          content:
            application/json:
              schema:
                type: object
                example:
                  error:
                    message: Not Found
                    code: 10003
        '422':
          description: ''
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ExceptionDto'
      security:
        - x_api_key: []
components:
  schemas:
    ReportIssuePayloadDto:
      type: object
      properties:
        reason:
          type: string
          description: What is wrong with this advert or property
          enum:
            - STILL_ONLINE
            - NOT_ONLINE_ANYMORE
            - WRONG_DATA
            - WRONG_LOCATION
            - DUPLICATE
            - WRONG_AGENCY
            - OTHER
          example: STILL_ONLINE
        comment:
          type: string
          description: >-
            Free-text details. Optional, except when `reason` is `OTHER` where
            it is required.
          maxLength: 1000
          example: The ad is still visible on seloger, you flagged it offline.
      required:
        - reason
    RecheckResponseDto:
      type: object
      properties:
        status:
          type: string
          enum:
            - accepted
            - nothing_to_check
          example: accepted
        entity:
          type: string
          enum:
            - advert
            - property
          example: property
        flx_id:
          type: string
          description: flx_id the request was made on
          example: '123456789'
        triggered:
          description: flx_id of every advert handed to the scraper
          example:
            - '987654321'
            - '987654322'
          type: array
          items:
            type: string
        triggered_count:
          type: number
          example: 2
        skipped_count:
          type: number
          description: >-
            Online adverts that were NOT re-checked: beyond the per-request cap,
            missing a source url, or dropped because too many scrapes are
            already running
          example: 0
        message:
          type: string
          example: 2 advert(s) queued for an on-demand re-check.
      required:
        - status
        - entity
        - flx_id
        - triggered
        - triggered_count
        - skipped_count
        - message
    ExceptionDto:
      type: object
      properties:
        error:
          description: Error object
          allOf:
            - $ref: '#/components/schemas/ErrorDto'
      required:
        - error
    ErrorDto:
      type: object
      properties:
        message:
          type: string
          description: Error message
        code:
          type: number
          description: Error code
      required:
        - message
        - code
  securitySchemes:
    x_api_key:
      type: apiKey
      in: header
      name: x-api-key

````