# Create a follow-up

Creates a follow-up linking a customer to a product.
Returns 409 if the follow-up already exists (customer already follows this product).

Endpoint: POST /customers/{customerId}/follow-ups/{productId}
Version: 1.6.0
Security: bearerAuth

## Security:

  - `bearerAuth` (unknown)
    http bearer opaque

## Path parameters:

  - `customerId` (integer, required)
    ID of the customer.

  - `productId` (integer, required)
    ID of the product to follow.

## Response 201:

  - `201` (unknown)
    Follow-up created

## Response 201 fields (application/json):

  - `data` (object)
    A follow-up links a customer to a product they are interested in.

  - `data.customerId` (integer)
    Customer ID.
    Example: 789

  - `data.productId` (integer)
    Product ID.
    Example: 12345

  - `data.opinion` (object)
    Agent's opinion on the match.

  - `data.opinion.value` (integer | null)

  - `data.opinion.text` (string | null)

  - `data.rating` (integer | null)
    Customer interest rating (0-5).
    Example: 4

  - `data.visibleCustomer` (boolean | null)
    Whether the follow-up is visible to the customer (portal).

  - `data.updatedAt` (string | null)
    Last update timestamp.

  - `data.progress` (string | null)
    Follow-up progress label.

## Response 403:

  - `403` (unknown)
    Access denied. The error `code` is always `FORBIDDEN`; the `message` gives the cause:
- `You do not have permission to perform this action.`
 — the access does not

hold the API pack / right required by the endpoint.
- `Insufficient scope for this request.`
 — the resource targeted by the request

(user, customer, product, agency, transaction, ...) is outside the scope of

the authenticated access.
- `Access denied for this editor.`
 /
`Your IP address has been blocked.`
 —

editor or IP restriction.

## Response 403 fields (application/json):

  - `error` (object)

  - `error.code` (string, required)

  - `error.message` (string, required)

## Response 409:

  - `409` (unknown)
    Follow-up already exists (customer already linked to this product)

## Response 409 fields (application/json):

  - `data` (object)
    A follow-up links a customer to a product they are interested in.

  - `data.customerId` (integer)
    Customer ID.
    Example: 789

  - `data.productId` (integer)
    Product ID.
    Example: 12345

  - `data.opinion` (object)
    Agent's opinion on the match.

  - `data.opinion.value` (integer | null)

  - `data.opinion.text` (string | null)

  - `data.rating` (integer | null)
    Customer interest rating (0-5).
    Example: 4

  - `data.visibleCustomer` (boolean | null)
    Whether the follow-up is visible to the customer (portal).

  - `data.updatedAt` (string | null)
    Last update timestamp.

  - `data.progress` (string | null)
    Follow-up progress label.

## Response 403 examples:

  - `Missing API pack / right` (unknown)

  - `Resource outside the scope of the access` (unknown)

