# 1.4.0 — 2026-10-07

## 1.4.0 — 2026-10-07
**Added**
- `GET /discovery`
 now returns a
`packs`
 array listing the API packs

(subscription scopes) attached to the authenticated access. Each pack

exposes
`name`
 and
`description`
.

**Changed**
- Anti-cold-calling consent proof files are now retained in cloud storage

(ImmoCloud) when consent is revoked or updated.
- Creating, updating, or revoking a contact's anti-cold-calling consent now

refreshes the contact's last-update date.
- The
`editeur_id`
 field has been removed from the discovery agency

payload.
- On the transaction search endpoints

(
`POST /transactions/agreement/search`
,

`/transactions/sales-offers/search`
,
`/transactions/leases/search`
),

`include`
 is now passed as a
**query parameter**
 (comma-separated)

instead of a request body field, for consistency with the rest of the

V2 API (e.g.
`GET /customers/{customerId}`
). An unknown include now

returns a
`422 INVALID_INCLUDE`
 error listing the available includes.

**Fixed**
- Transaction search endpoints (
`POST /transactions/agreement/search`
,

`/transactions/sales-offers/search`
,
`/transactions/leases/search`
) now

accept several comma-separated values in
`include`
 (e.g.

`include=buyer,seller,fees`
). Previously, only a single include was

accepted and multiple values returned a
`422 VALIDATION_ERROR`
.
- `GET /customers/{customerId}?include=color`
 now returns the contact's

color instead of
`null`
 when the agency uses the default color

configuration.
- Uploading a consent proof file no longer fails silently. If a proof file

cannot be stored, the request now returns
`502`
 and the consent is not

recorded, instead of succeeding without the proof.
- Discovery documentation now correctly reflects the actual response

structure
`{ agencies: [...], packs: [...] }`
 (was incorrectly

documented as
`{ data: [...] }`
).

**Deprecated**
- Discovery agency field
`manufacturer_id`
 is deprecated in favor of

`agency_id`
. It remains present for backward compatibility and will be

removed in a future major release.

Version: 1.6.0
Security: bearerAuth

## Description:

  - `1.4.0 — 2026-10-07` ()
    **Added** - `GET /discovery`
 now returns a
`packs`
 array listing the API packs

(subscription scopes) attached to the authenticated access. Each pack

exposes
`name`
 and
`description`
. **Changed** - Anti-cold-calling consent proof files are now retained in cloud storage

(ImmoCloud) when consent is revoked or updated.
- Creating, updating, or revoking a contact's anti-cold-calling consent now

refreshes the contact's last-update date.
- The
`editeur_id`
 field has been removed from the discovery agency

payload.
- On the transaction search endpoints

(
`POST /transactions/agreement/search`
,

`/transactions/sales-offers/search`
,
`/transactions/leases/search`
),

`include`
 is now passed as a
**query parameter**
 (comma-separated)

instead of a request body field, for consistency with the rest of the

V2 API (e.g.
`GET /customers/{customerId}`
). An unknown include now

returns a
`422 INVALID_INCLUDE`
 error listing the available includes. **Fixed** - Transaction search endpoints (
`POST /transactions/agreement/search`
,

`/transactions/sales-offers/search`
,
`/transactions/leases/search`
) now

accept several comma-separated values in
`include`
 (e.g.

`include=buyer,seller,fees`
). Previously, only a single include was

accepted and multiple values returned a
`422 VALIDATION_ERROR`
.
- `GET /customers/{customerId}?include=color`
 now returns the contact's

color instead of
`null`
 when the agency uses the default color

configuration.
- Uploading a consent proof file no longer fails silently. If a proof file

cannot be stored, the request now returns
`502`
 and the consent is not

recorded, instead of succeeding without the proof.
- Discovery documentation now correctly reflects the actual response

structure
`{ agencies: [...], packs: [...] }`
 (was incorrectly

documented as
`{ data: [...] }`
). **Deprecated** - Discovery agency field
`manufacturer_id`
 is deprecated in favor of

`agency_id`
. It remains present for backward compatibility and will be

removed in a future major release.

