Data Principal Requests & Grievances
Beyond consent, DPDPA-style regulation gives principals the right to request access to, correction of, or erasure of their data (a Data Principal Request, or DPR, also called a DSR request in the API paths), and to file a grievance if they feel their rights aren't being honored. The public API lets you surface both flows in your product.
DSR requests
A DSR request has one of four types:
| Type | What it means |
|---|---|
ACCESS | "Send me a copy of everything you have on me" |
CORRECTION | "Some of my data is wrong, please fix it" |
ERASURE | "Delete my data" |
NOMINATION | "In the event I'm unable to exercise my rights, this person may act on my behalf" |
Submitting one is a single call, gated on the principal's session token like every other principal-scoped endpoint (see Authentication):
curl -X POST "$CMP_BASE/dsr" \
-H "X-Org-Api-Key: $CMP_KEY" \
-H "X-Principal-Token: $PRINCIPAL_TOKEN" \
-H "Content-Type: application/json" \
-d '{ "type": "ACCESS", "payload": "Please send my data as a CSV." }'
The response includes a referenceId in the format DSR-yyyyMMdd-XXXXX — show this to the principal and let them
check its status later (still requires their own token — a referenceId alone isn't enough to read someone else's
request):
curl "$CMP_BASE/dsr/status/DPR-20260704-VY2ZT" \
-H "X-Org-Api-Key: $CMP_KEY" \
-H "X-Principal-Token: $PRINCIPAL_TOKEN"
Status lifecycle
PENDING → ACKNOWLEDGED → FULFILLED
↘ REJECTED
Acknowledging and fulfilling/rejecting a request are admin-facing actions (done from the Bytemonk dashboard's DSR Requests page by the org's DPO) — the public API only lets a principal submit a request and check its status, not act on it. Design your UI to poll or link to the status-check endpoint rather than expecting an immediate resolution.
A principal can also list their own DSR history in one call — GET /dsr — rather than tracking every
referenceId they've ever received. It's paginated like the admin API (?page=0&size=20); see
List my DSR requests.
Full field reference: DSR API.
External ticketing (optional, admin-configured)
If an org has connected an external ticketing tool (currently Jira) from the dashboard's CMP Settings, every new
DSR request automatically opens a matching ticket there — due date included — and its open/closed state is kept
in sync automatically as the ticket moves through the org's own workflow. You don't need to build anything for
this: it shows up as automatic SYSTEM-authored entries ("Jira ticket ABC-123 created."/"...closed.") in the
request's communication thread, the same thread principal and DPO
messages already appear in. There's no public endpoint for configuring or reading the ticket connection itself —
it's entirely a dashboard/admin-side setting.
Grievances
A grievance is a complaint — optionally linked to a specific DSR request it's about (linkedDsrId), with a
category:
| Category | Meaning |
|---|---|
CONSENT_NOT_HONORED | "You're using my data for something I didn't consent to" |
DATA_BREACH_CONCERN | A suspected or reported breach |
DSR_NOT_FULFILLED | A DSR request wasn't handled properly or in time |
TARGETING_MINOR | Concern about a minor being targeted without proper guardian consent |
OTHER | Anything else |
curl -X POST "$CMP_BASE/grievances" \
-H "X-Org-Api-Key: $CMP_KEY" \
-H "X-Principal-Token: $PRINCIPAL_TOKEN" \
-H "Content-Type: application/json" \
-d '{
"subject": "Marketing emails after I opted out",
"description": "I withdrew marketing consent last week but still received a promotional email today.",
"category": "CONSENT_NOT_HONORED"
}'
Like DSRs, grievances get a referenceId (format GRV-yyyyMMdd-XXXXX) for status checks, and their
acknowledge/resolve/escalate lifecycle is admin-facing only.
Status lifecycle
OPEN → ACKNOWLEDGED → RESOLVED
↘ ESCALATED_TO_DPB
(DPB = Data Protection Board, the regulatory body a grievance can be escalated to under DPDPA if the org doesn't
resolve it satisfactorily.)
Like DSRs, a principal can list every grievance they've filed via GET /grievances, paginated the same way — see
List my grievances.
Full field reference: Grievances API.
Grievances get the same optional external-ticketing treatment as DSR requests — see
External ticketing above; the same SYSTEM-authored
created/closed entries appear in a grievance's own
communication thread.