What is Consent 2.0

Take a moment to remind yourself about what exactly is the Consent feature on the APSIS One platform by reading this Help Center article.

Consent 1.0


Current version

Consent 1.0 is the current, generally available release of this functionality

Currently the APSIS One platform as well as One API support version 1.0 of the Consent functionality. In order for a Profile to receive communication, the following actions must take place in Consent 1.0:

  • An Opt-In Consent to a specific Topic is given on the Channel and Address level (or just on the Address level for Channel Specific Topics)
  • Since a Profile and an Address are not the same things, a Subscription must also be created to assign the Profile to the Topic

This makes integrating with Consent via One API complex.

Consent 2.0


In beta

Consent 2.0 is currently in beta testing. While the specification for the related One API endpoints should not change, this guide gets updated from time to time so check back now and then for more information.

With Consent 2.0, if you want a Profile to receive communication, there's just one step to complete:

  • An Opt-In Consent to a specific Topic over a specific Channel is given on the Profile level

Isn't that simpler? Here's a summary of changes brought by Consent 2.0:

  • Consent is given on a Profile level, not on an Address level
  • Consent hierarchy support is removed, which enabled the following two changes
  • API for Consent management is simplified
  • Performance is significantly improved


Have questions?

Contact [email protected] to learn more