17 February

We are working on some important updates related to our Consent Model. It is important that you are aware of this change in case you need to accommodate your system.

timeline

This announcement was made on the {a-date}.
We expect to release these changes into production on approximately the 15 March.

The translations property, which is currently an array (Current Consent Model), will become a map (New Consent Model) where the key is the code language. Thus, the lang_code property in the translation object will be removed. Check out the tabs below to get a visual of the changes.

  • Current Consent Model

  • New Consent Model

{
  "translations": [
    {
      "lang_code": "en",
      "description": "Tickets newsletter (on-sale dates, special offers).",
      "title": "Tickets newsletter"
    },
    {
      "lang_code": "es",
      "description": "Entradas newsletter (fechas de venta, ofertas esclusivas).",
      "title": "Newsletter entradas"
    }
  ],
  "description": "La newsletter billeterie (date d'ouvertures des ventes matchs, offres exclusives).",
  "title": "Newsletter billeterie",
  "key": "billeterie",
  "consent_type": "opt-in"
}
{
  "translations": {
    en: {
      "description": "Tickets newsletter (on-sale dates, special offers).",
      "title": "Tickets newsletter"
    },
    es: {
      "description": "Entradas newsletter (fechas de venta, ofertas esclusivas).",
      "title": "Newsletter entradas"
    }
  },
  "description": "La newsletter billeterie (date d'ouvertures des ventes matchs, offres exclusives).",
  "title": "Newsletter billeterie",
  "key": "billeterie",
  "consent_type": "opt-in"
}

API impact

Consents can be managed by the Management API (see the Consents section). The expected responses will now change to reflect the latest development around translations.

Affected endpoints: