Release Notes

This is a list of changes introduced between version 3 and version 1 of our APIs

General changes

Caching

An internal change has been made with how we cache individual resources (Fragment cache) and endpoints (Endpoint cache) to generalize it’s behaviour. This should have no impact on usage.

We will now more consistently support the header for Cache-Control when it is set to no-cache

Erroring

Errors are now more consistent in their format: Type field now included in error responses RFC7807

Localization (And translations)

While Version 1 supports Dynamic Translations (configurable through the #translations-api the way we identify which language we should provide the content with has changed.

  • v1 : first pick language from the locale URI param, then the language on the session (remembering the last time you used the language param), then the ACCEPT Headers
  • v3 : first pick language from the locale URI param, then the ACCEPT Headers, finally the language of the company

NOTE : remembering the language from the session was deprecated on this version

Before you were not able to control the language through the headers after the first call, this has changed on v3, and now using the Accept headers is our preferred method of setting the client’s language.

Vary header now varies on Accept-Language


API Specific changes

Service API and resources

Services time link now point ot time API rather than time data (ADMIN only): Exposes whether the service is configured for multi-locations

Attendee API (Admin)

Include additional staff members

Time API

We have enabled support for multi-location appointments. This are appointments that take resources or people from more than one company. The configuration of the start_time_requirements determines which branches to take resources or people from

Basket API

On the Baskets, we have enabled support for multi-location appointments