Get subscriptions from the API and withdraw consents

RE: Get subscriptions from the API and withdraw consents

Hi Stian,

Yes, the person webhooks do support notification when a person consent change.

Get the Purpose items (use the Key to get STORE or EMARKETING):

GET /api/v1/List/ConsentPurpose/Items​

GET /api/v1/List/ConsentSource/Items

GET /api/v1/List/LegalBase/Items​

GET /api/v1/List/ShipmentType/Items

@query = consentperson.person_id
@filter = consentperson.consentpurpose_id eq 2
GET /api/v1/archive/dynamic?$select={{query}}&$filter={{filter}}
Authorization: Bearer {{token}}
Content-Type: application/json
Accept: application/json​

@query = consentperson.person_id
@filter = consentperson.person_id in (5,7,17) and consentperson.consentpurpose_id eq 2 and 

GET /api/v1/archive/dynamic?$select={{query}}&$filter={{filter}}
Authorization: Bearer {{token}}
Content-Type: application/json
Accept: application/json​

@filter1 = consentPerson/person/personId in (7,17) 
@select1 = consentPerson/person/personId,active,key,name,consentPerson/comment
GET /api/v1/Archive/ConsentPurpose?$select={{select1}}&filter={{filter1}}
Authorization: Bearer {{token}}
Content-Type: application/json
Accept: application/json

RE: Get subscriptions from the API and withdraw consents

Thank you very much for the reply!

Is there some documentation for the specific entities? So that I can select more fields from the persons also when using that dynamic endpoint? I guess that the query:

v1/archive/dynamic?$select=consentperson.person_id&$filter=consentperson.consentpurpose_id eq 2

Retrieves all person that has given an emarketing consent, could you also select legalbase, emails, mobilephones, fullname etc too? I couldn't manage to create such a query. That would simplify some logic we have in our app.

RE: Get subscriptions from the API and withdraw consents

Hi Stian,

Using the dynamic provider is the closest you can get to issuing raw sql queries to the database. All of the available fields you use to construct the query are not from pre-defined archive providers, which have their own "available (supported) columns" definitions. With the dynamic archive provider you must use what's referred to as DotSyntax, a query-like construct where you specify fields directly from the database. 

Here is a link to the docs about how to use the DotSyntax query syntax. Although this info resides in the Customer Service docs, it's the same content that matters.

Here is a link the database reference guide, and list of tables.

Couple [advanced] Examples:

• From users (associates) to email address
• From extra tables to person information

Hope this helps!