Migration of the endpoint POST /v0/subscriptions to POST /v1/subscriptions

Context

Upgrade from POST - /v0/subscriptions to POST - /v1/subscriptions

⭐ Key benefit :

• Deletion of deprecated and unuseful fields, to make the endpoint easier to use

Impacts

Route to call :

• POST - /v1/subscriptions

Input became

{
  "email": "name@email.com",
  "gender": "M",
  "civility_code": "MR",
  "first_name": "Jean",
  "unicode_first_name": "牛仔裤",
  "last_name": "Chang",
  "unicode_last_name": "昌",
  "phone": "+33145789632",
  "birthdate": "1999-12-20",
- "birthday": "20100430",
- "legal_informations": [
-   {
-     "id": "general_selling_notice",
-     "agreement": true
-   }
- ],
  "optins": [
    {
      "channel": "EMAIL",
      "optin": true,
-     "optin_partners": true
    }
  ],
  "origin_code": "CUSTOMER_ACCOUNT",
  "newsletter_subscriptions": [
    "CLUBMED"
  ]
}

• We deleted birthday which was deprecated
• We deleted legal_informations because the customer's agreement is mandatory for newsletter subscriptions anyway, and the array of optins already allows us to confirm that the customer accepted the optins
• We deleted the optin_partners, which is no longer used and therefore irrelevant
• We made optins and newsletter_subscriptions mandatory, to avoid errors