Skip to content

Demo environment · sample data

Data Consent Manager

For developers

One API. Every answer signed.

Connect your systems to Data Consent Manager with a small REST API and signed webhooks. Your developers can have a first integration running in the sandbox in a few days.

How it fits together

Four things your systems do

  1. 1

    Ask

    Create a consent request

    Send the person to the journey URL we return. They decide on our screen, in their language.

  2. 2

    Check

    Check before you use data

    One call tells you whether a consent is active and which purposes it allows, right now.

  3. 3

    Listen

    Receive signed webhooks

    We tell you the moment a consent is given, refused or withdrawn. You confirm each withdrawal.

  4. 4

    Share

    Exchange data, sealed

    Move data to another company encrypted for them alone, tied to the person's consent.

In practice

Ask for consent, then check it

1 · Create a consent request
# Your API key goes in the Authorization header
curl -X POST https://api.demo.dataconsentmanager.com/v1/consent-requests \
  -H "Authorization: Bearer dcm_sk_…" \
  -d '{
    "notice_id": "ntc_01J…",
    "validity_days": 365,
    "return_url": "https://bank.example/done"
  }'

# Response: send the person to journey_url
{ "request_id": "req_01J…", "state": "REQUESTED",
  "journey_url": "https://demo.dataconsentmanager.com/journey/req_01J…" }
2 · Check it before you use the data
# Ask us, every time, before processing
curl https://api.demo.dataconsentmanager.com/v1/consents/cns_01J…/status \
  -H "Authorization: Bearer dcm_sk_…"

{
  "status": "ACTIVE",
  "granted_purposes": ["credit-check"],
  "valid_until": "2027-11-19T00:00:00Z",
  "as_of": "2026-11-19T10:42:01Z"
}
3 · Webhook we send you when a person withdraws
# Header X-DCM-Signature: compact ES256 JWS over the body. Verify it with our JWKS.
POST https://bank.example/hooks/consent

{
  "specversion": "1.0", "id": "evt_01J…",
  "type": "in.dataconsentmanager.consent.withdrawn",
  "subject": "cns_01J…",
  "data": { "ack_required": true, … }
}

# Then confirm you stopped processing:
POST /v1/events/evt_01J…/ack { "action": "PROCESSING_STOPPED" }

Reference

The endpoints

Every call uses HTTPS and JSON. Every record and event we send is signed with keys you can fetch and check yourself.

POST/v1/consent-requestsStart a consent journey for a notice and its purposes
GET/v1/consent-requests/{id}Follow a request until the person decides
GET/v1/consents/{id}/statusLive status and the purposes allowed right now
GET/v1/consents/{id}The signed consent record (compact JWS)
POST/v1/webhooksRegister the HTTPS endpoint that receives events
POST/v1/events/{id}/ackConfirm you acted on an event, for example stopped processing
POST/v1/noticesPublish a notice with its purposes and languages
POST/v1/exchange/sessionsOpen a data-blind exchange with another company
GET/.well-known/jwks.jsonOur public keys, to verify every signature yourself

Built in

What you do not have to build

  • Notices in 23 languages

    English and the 22 languages of the Eighth Schedule, versioned, with a fingerprint of exactly what the person saw.

  • Proof for audits

    A signed record for every decision and a tamper-evident ledger, so you never have to defend your own logs.

  • Retries and escalation

    Webhooks follow the CloudEvents standard and are retried with back-off. Unconfirmed withdrawals are escalated.