Consent Endpoints are necessary to support the basic integration of Fast Track. The instructions on how to send them are listed below. GET & POST endpoints are required.
⬇️ 1. GET /userconsents/:userid
The Operator needs to provide Fast Track with the UserConsents endpoint to fetch user consent 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.
Please note that the type is CASE sensitive. Speak with your integrations manager if you would like to change the format. Kindly always check the request when testing.
All consent types need to be included in the response. If consents are not used, please return either "true" or "false".
⬆️ 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 directives 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.
Example request (from Fast Track)
We will only request one consent update at a time.