Quickstart

Quickstart: record marketing and data consent

POST /public/v1/consent records a user's consent choices at the point of collection. Capture the consent alongside an enquiry so every downstream contact respects the user's decision — and you have a timestamped, auditable record of exactly what they agreed to.

2 min read

POST/public/v1/consent

auditableTimestamped record

granularPer-purpose flags

Record the choices

curl -s -X POST https://api.credicorp.co.uk/public/v1/consent \
  -H 'Content-Type: application/json' \
  -d '{
    "email": "[email protected]",
    "purposes": { "marketing_email": true, "marketing_sms": false },
    "source": "partner-widget"
  }'

Consent is stored per purpose so you can honour a user who wants product updates but not SMS. The response echoes the stored record with a server timestamp you can log for your own audit trail.

Capture it at the source

Record consent at the exact moment it is given — the same form that submits the enquiry — and pass a meaningful source so you can trace where each consent originated.

Frequently asked questions

Do I need consent to submit an enquiry?

You need a lawful basis to process the enquiry itself; separate marketing consent is what this endpoint records. Keep the two decisions distinct on your form.

Can a user change their mind later?

Yes. Record the updated choices with another call; the latest record for a given email is authoritative, and the history is retained for audit.