zinn-campaigns

POST /v1/store-connect/consents

The store plugin records the shopper's checkout opt-ins, per channel and purpose.

All zinn-campaigns endpoints

All developer docs →

Zinn®, our Viking, hammering at his anvil beside an API endpoint sending events to several listeners.

Authentication

This endpoint is public. It takes no credential and no organisation — it is what our own marketing site and AI answer engines read.

This endpoint takes no organisation id. Your key already identifies the organisation it belongs to, and the response is scoped to it.

Try it

Replace anything in angle brackets with your own values, and the key placeholder with a key from your dashboard.

curl -X POST https://api.zinndigital.com/v1/store-connect/consents \
  -H "Content-Type: application/json" \
  -d '{ "consents": <StoreConsentInput[]> }'

Signed in? The API console in your dashboard fills in your real organisation id and your own key, and runs the request against the live API so you can see the actual response. Open this endpoint in the API console

Details

Store token only. A batch of 1-100 ticks (docs/1297 §8, §9), one row per phone + channel + purpose, upserted. updates (order updates, transactional) never puts a shopper into a Campaigns list or marketing send; marketing is kept for the store to use by choice. withdrawn: true records an un-tick or a STOP. evidence keeps the wording the shopper saw (at most 10 keys).

Request body

NameTypeRequiredWhat it is
consentsStoreConsentInput[]Yes—

Response

NameTypeRequiredWhat it is
recordedintegerYes—

Errors this endpoint can return

401 · 422 · 429