Bytemonk CMP — Developer Documentation
Bytemonk's Consent Management Platform (CMP) lets an organization author versioned, multilingual consent notices, collect purpose-level consent from data principals (your end users), and manage Data Principal Requests (DPR) requests and grievances — in line with India's Digital Personal Data Protection Act (DPDPA) and similar consent regimes (GDPR, etc.).
This site documents the public, API-key-authenticated surface of the CMP — the part you integrate against from your own website, mobile app, or backend to:
- Register a data principal and mint them a short-lived session token
- Fetch the currently active consent notice for display in a banner/widget
- Grant or withdraw purpose-level consent
- Check a principal's current consent status
- Submit and track Data Principal Requests (DPR)
- File and track grievances
There are two supported integration patterns, using two different API key types — see Authentication for the full picture:
- Browser widget (anonymous, no login) — Quickstart and Embedding a Widget. Uses a Publishable key.
- Server-side, on behalf of an already-logged-in user — Server-Side Integration. Uses a Secret key, called from your own backend.
The CMP has a separate admin-facing API (session-authenticated, used by the Bytemonk dashboard for org admins to author notices, review DSRs, etc.) which is not covered here. This site is exclusively for the public API — the one your website/app talks to on behalf of your end users.
Where to start
- New integration? Start with Quickstart — a 10-minute walkthrough that gets you from "no code" to a working consent banner.
- Want to understand the model first? Read Core Concepts — what a "notice", "purpose", and "consent record" actually mean here, and how they relate.
- Just need the endpoint reference? Jump straight to the API Reference.
- Debugging an error? See the Error Codes reference.
Base URL
https://api.bytemonk.co/api/v1/public/cmp
All endpoints on this site are relative to that base URL. If you're testing against a local/self-hosted deployment,
substitute your own host (e.g. http://localhost:9090/api/v1/public/cmp).