# 1.6.0 — 2026-11-12

## 1.6.0 — 2026-11-12
**Added**
- New outbound **calendar** webhook event. Immofacile now sends an HTTP
`POST` to your registered URL when a subscribed calendar event occurs
(`CALENDAR_CREATE`, `CALENDAR_UPDATE`, `CALENDAR_DELETE`). Requires the
`MODULE_IMMO_AGENDA` module.
- The contact search endpoint `POST /customers/search` now accepts the
`include` query parameter (comma-separated) to load additional relations
on each returned contact, consistent with `GET /customers/{customerId}`.
Available includes: `address`, `groups`, `color`, `origin`, `user`,
`gender`, `stopSms`, `notary`, `relations`, `subscriptions`,
`searchRequests`, `agency`, `consent`, `mandate`, `website`. An unknown
include returns a validation error listing the available includes.
- New endpoints added to the documentation:
  - `GET /actions/{actionId}`
 — logged actions of a given action type, optionally for one customer or product.
- Webhook documentation completed: the `CUSTOMER_CREATE`, `CUSTOMER_UPDATE`,
`PRODUCT_CREATE`, `PRODUCT_UPDATE` and `CALENDAR_*` events are documented, with the
`origine` enum on `POST /hooks` and `PUT /hooks/{hookId}`.

**Changed**
- Webhook payload documentation corrected to match what is actually sent:

`{timestamp, origine, client_id, site_ids, data}`
 instead of

`{event_type, resource_id, timestamp}`
.
- Webhook delivery rules clarified: 4xx responses (including
`422`
) are not

retried, only 5xx, timeouts and network errors are (up to 3 times); the

response timeout is 60 seconds; the
`format`
 field accepts
`immofacile`

(default) or
`zapier`
.
- Calendar event
`type`
 is now documented as the event type identifier

(e.g.
`"7"`
) rather than the event type key (e.g.
`VISIT`
), to match the

actual payload returned by the agenda endpoints.

Version: 1.6.0
Security: bearerAuth

## Description:

  - `1.6.0 — 2026-11-12` ()
    **Added** - New outbound **calendar** webhook event. Immofacile now sends an HTTP
`POST` to your registered URL when a subscribed calendar event occurs
(`CALENDAR_CREATE`, `CALENDAR_UPDATE`, `CALENDAR_DELETE`). Requires the
`MODULE_IMMO_AGENDA` module.
- The contact search endpoint `POST /customers/search` now accepts the
`include` query parameter (comma-separated) to load additional relations
on each returned contact, consistent with `GET /customers/{customerId}`.
Available includes: `address`, `groups`, `color`, `origin`, `user`,
`gender`, `stopSms`, `notary`, `relations`, `subscriptions`,
`searchRequests`, `agency`, `consent`, `mandate`, `website`. An unknown
include returns a validation error listing the available includes.
- New endpoints added to the documentation:
  - `GET /actions/{actionId}`
 — logged actions of a given action type, optionally for one customer or product.
- Webhook documentation completed: the `CUSTOMER_CREATE`, `CUSTOMER_UPDATE`,
`PRODUCT_CREATE`, `PRODUCT_UPDATE` and `CALENDAR_*` events are documented, with the
`origine` enum on `POST /hooks` and `PUT /hooks/{hookId}`. **Changed** - Webhook payload documentation corrected to match what is actually sent:

`{timestamp, origine, client_id, site_ids, data}`
 instead of

`{event_type, resource_id, timestamp}`
.
- Webhook delivery rules clarified: 4xx responses (including
`422`
) are not

retried, only 5xx, timeouts and network errors are (up to 3 times); the

response timeout is 60 seconds; the
`format`
 field accepts
`immofacile`

(default) or
`zapier`
.
- Calendar event
`type`
 is now documented as the event type identifier

(e.g.
`"7"`
) rather than the event type key (e.g.
`VISIT`
), to match the

actual payload returned by the agenda endpoints.

