TrustCommander
Community home
Search…
English
Overview
Responsability of actors
Releases notes
Setup Guides
Tag Manager
Websites (Hardcoded)
Mobile apps
User Guides
Categories & Tags
Privacy Banners
Dashboard
Exports
Options
Extensions
Cookie Scanner
TagFirewall
Tag Hierarchy
Marketing Preferences Center
Marketing Preferences Center (Trust Premium only)
Knowledge Base
Consent Object
TrustCommander cookies exemption
Consent Cookie
IAB TCF V2.0 Consent
IAB TCF V2.0 and Google FAQ
Rest data API
GET/PUT Consents / preferences
Onsite API
Getting Started
consent.get
consent.update
consent.revoke
consent.onUpdate
PLATFORM API
Get statistics
Powered By
GitBook
GET/PUT Consents / preferences
Get/put user consent stored in DataCommander
get
https://api.commander1.com
/engage/user/
User Consents
get
https://api.commander1.com/v1.0
/engage/visitors/
Visitor Consents
put
https://api.commander1.com
/engage/user/
User
Syntax and limitations
The json playload is represented by a key/value for each preference.
Each preference property (key) start with "preferences." followed by the preference name :
preferences.your_preference_name
The preference name should not contain white space, dot or special characters. Its format is
[A-Za-z0-9_-]
The preference value can contain white space, dot but not special characters.
The API accepts a
maximum of 20 preferences
Example Request
PUT
https://api.commander1.com/engage/user/?site=1234&user_id=1234&token=WvNIX8955cnZ7WF0f632s0Wb99Ql3rtA
1
{
2
"preferences": {
3
"news_monthly": true,
4
"news_sales": true
5
}
6
}
Copied!
Knowledge Base - Previous
IAB TCF V2.0 and Google FAQ
Next - Onsite API
Getting Started
Last modified
5mo ago
Export as PDF
Copy link
Contents
get
User Consents
get
Visitor Consents
put
User