Release note - v0.3389.1 ... v0.3392.0

Highlights

• Added two optional parameters customer_id and opportunity_id in POST/v0/outbound_phone_calls to improve the synchronization of outbound calls
• New NDCx identifier added in the enumeration of legal information from GET/v0/legal_info
• Display of transfer comments in the response from GET/v3/customers/{customer_id}/bookings/{booking_id}/services
• Improved mapping of Russian opt-ins in GET/v0/subscriptions/{subscription_id}

Detail of v0.3392.0

This version brings two major functional improvements:

Enrichment of outbound calls

The POST/v0/outbound_phone_calls route now accepts two new optional parameters in the request body:

• customer_id (string, optional): identifier of the contact called
• opportunity_id (string, optional): identifier of the business opportunity associated with the call

These parameters make it easier to synchronize outbound calls with the CRM and ensure more complete and consistent data. Both fields can be transmitted empty or omitted.

Extension of legal information

The GET/v0/legal_info route sees its enumeration of the id field extended with a new value: NDCx, bringing the total number of legal identifiers supported to 35.

Detail of v0.3391.0

This version improves the visibility of transfer information for booking services.

Transfer comments

The GET/v3/customers/{customer_id}/bookings/{booking_id}/services route now exposes a new comment field in the transfer_information object. This mandatory field (string, 30 characters maximum) contains any specific comments regarding the transfer.

If no comment is present in the source data, the field is returned with an empty string.

Detail of v0.3390.0

This version improves the management of Russian opt-ins for newsletter retrieval.

Mapping of RUSSIA opt-ins

The GET/v0/subscriptions/{subscription_id} route now applies consistent mapping for the RUSSIA opt-in channel:

• When the value RUSSIA is received from the source system, it is automatically transformed into CONFORMITY in the API response
• Exception: if the API key used corresponds to the BE application, the value is transformed into CGU_2

This evolution completes the work previously carried out on the newsletter subscription and unsubscription routes, and ensures consistency in the mapping of opt-ins across all relevant routes.