post deprecatedhttps://api.apsis.one/audience/channels//addresses//consents
Consent 1.0 is being deprecated
This feature is a part of Consent 1.0 functionality in APSIS One that will soon be replaced by Consent 2.0.
See this page to understand how to proceed with your existing and new integrations.
Create a consent
Supported consents types:
| type | consent level |
|---|---|
opt-in | topic |
opt-out | account, section, topic |
Supported consent levels:
| level | required properties |
|---|---|
| account | type |
| section | type, section_discriminator |
| topic | type, section_discriminator, consent_list_discriminator, topic_discriminator |
For a profile to receive your communication, the following requirements must be met:
- profile's address has a topic level opt-in consent (see
/audience/channels/{channel_discriminator}/addresses/{address}/consentsendpoint) - profile is subscribed to the topic (see
/audience/keyspaces/{keyspace_discriminator}/profiles/{profile_key}/sections/{section_discriminator}/subscriptionsendpoint)
If a topic provided in the request body is channel-specific then its channel_discriminator obtained from the definitions endpoint must match the channel_discriminator from this request path.
Read more about Consent 1.0 in this Help Center article.