v1.1.1 - [03-10-2019]

3, October 2019


Collection Responses

(breaking change)

The data property was renamed to items to better represent its content.

Automatic string localization

Auto localized strings where introduced in a previous release, below are the followed rules for this system:

  • Uses a supported language if found in the Accept-Language header
  • Otherwise, uses the Platform's default language


(breaking changes)

This release marks the first stable catalog queries. It is now safe to implement them as they should not undergo major breaking changes in the future.

Removed videos and extracts base queries

These queries were removed from the base catalog domain. You should now use the products query to list your products and access their videos/extracts.

To access the videos/extracts of a set of products, you can use the includeIds argument:

catalog {
    # Get products 1 & 4
    products (includeIds: [1, 4]) {
        items {
            videos {
            extracts {

Localized product prices

Prices of products are now localized, based on the following rules :

  • Authenticated users :
    • Uses the user's country currency if supported
    • Uses the currency of the user's country from IP Address if supported
    • Otherwise uses the platform's default currency
  • Unauthenticated users :
    • Uses the currency of the user's country (from IP Address) if supported
    • Otherwise uses the platform's default currency

This behavior might change in the future to use the Accept-Language header when suitable instead of the user's IP address.

Example of responses for a product purchase modes, given that the EUR, USD and JPY currencies are enabled :

Client with France IP Client with USA IP Client with Japan IP

Data Sync


Subscription models are now synched with the administration.

Known issues

You might have been experiencing synching issues between the administration and GQL. The synchronization system is still a work in progress and is expected to become stable by the end of October.

In the meantime, you can :

  • Try solving the issue by :
    • Editing the object in the administration, using an edit + save (it is not required to do any modification on the object).
    • Clicking on the save button will trigger a notification that should update your GQL Object.
  • If it did not work or if too many models have synching issues, you can open a Support Ticket to ask for a GQL cache rebuild.