# Customer event

Sent to your registered URL when a subscribed **customer** event occurs.
| `origine` | Trigger | Extra `data` fields |
|  --- | --- | --- |
| `CUSTOMER_CREATE` | A customer is created | `customer_group`, `customer_gender`, `action` |
| `CUSTOMER_UPDATE` | A customer is modified | none |

The customer identifier is always in `data.customers_id`.
Fetch the full resource with `GET /customers/{customerId}` if you need more details.
Delivery rules (acknowledgement, retries, suspension) are described on `POST /hooks`.

Endpoint: POST customerEvent
Version: 1.6.0
Security: bearerAuth

## Security:

  - `bearerAuth` (unknown)
    http bearer opaque

## Request fields (application/json):

  - `timestamp` (string, required)
    When the event occurred (ISO 8601).
    Example: 2026-09-11T14:30:00+02:00

  - `origine` (string, required)
    Event type a webhook can subscribe to. `CALENDAR_*` events are only
available when the `MODULE_IMMO_AGENDA` module is enabled.
    Enum: "CUSTOMER_CREATE", "CUSTOMER_UPDATE", "PRODUCT_CREATE", "PRODUCT_UPDATE", "CALENDAR_CREATE", "CALENDAR_UPDATE", "CALENDAR_DELETE"

  - `client_id` (integer, required)
    Identifier of your API client (the one that registered the webhook).
    Example: 12

  - `site_ids` (array, required)
    Sites the affected resource belongs to.
    Example: [3]

  - `data` (object, required)
    Identifies the affected resource and carries event-specific details.
| Event family | Identifier key |
|  --- | --- |
| Customer | `customers_id` |
| Product | `products_id` |
| Calendar | `event_id` |

Additional fields are described on each event. When the webhook uses
the `zapier` format, `data` also embeds the full customer or product.
    Example: {"customers_id":789}

## Response 200:

  - `200` (unknown)
    Event acknowledged.

## Response 422:

  - `422` (unknown)
    Resource intentionally rejected by the receiver (not retried).

