User Consents

⬇️ 1. GET /userconsents/:userid

The Operator needs to provide Fast Track with the UserConsents endpoint to fetch user consents data at relevant times in the user lifecycle. This ensures that the Operator complies with relevant data privacy directives and laws. FT CRM will fetch up to date consents on Registration, Login and User Update, and can also update consents in the case of unsubscriptions.

Response

    
{
  "consents": [
    {
      "opted_in": true,
      "type": "email"
    },
    {
      "opted_in": true,
      "type": "sms"
    },
    {
      "opted_in": false,
      "type": "telephone"
    },
    {
      "opted_in": true,
      "type": "postMail"
    },
    {
      "opted_in": true,
      "type": "siteNotification"
    },
    {
      "opted_in": true,
      "type": "pushNotification"
    }
  ]
}
  

⬆️ 2. POST /userconsents/:userid

The Operator should provide Fast Track with the UpdateUserConsents endpoint to update user consents at relevant times in the user lifecycle. This is to ensure that the Operator complies with relevant data privacy directive and laws. FT CRM will provide an Unsubscribe page that will be linked from SMS and Emails. When a user unsubscribes, FT CRM must also update the Operator platform setting.

Request

    
{
  "consents": [
    {
      "opted_in": true,
      "type": "email"
    },
    {
      "opted_in": true,
      "type": "sms"
    },
    {
      "opted_in": false,
      "type": "telephone"
    },
    {
      "opted_in": true,
      "type": "postMail"
    },
    {
      "opted_in": true,
      "type": "siteNotification"
    },
    {
      "opted_in": true,
      "type": "pushNotification"
    }
  ]
}
  

Response

    
OK 200
ERROR 400/500
  

​