Endpoint
Authentication
Requires a developer API key in theAuthorization header.
Request Headers
| Header | Value |
|---|---|
Authorization | Bearer <api_key> |
Content-Type | application/json |
Request Body
| Field | Type | Required | Description |
|---|---|---|---|
dataPrincipalId | string | Yes | The data principal filing the grievance |
type | string | Yes | Grievance type (e.g., "consent-violation", "data-breach", "unauthorized-processing") |
description | string | Yes | Detailed description of the grievance |
recordId | string | No | Related consent record ID (if applicable) |
evidence | object | No | Supporting evidence as a JSON object |
Example Request
Response — 202 Accepted
Response Fields
| Field | Type | Description |
|---|---|---|
grievanceId | string | Unique grievance ID |
referenceNumber | string | Human-readable reference number (format: GRV-YYYY-NNNNN) |
type | string | Grievance type |
status | string | Initial status: submitted |
expectedResolutionBy | string | ISO-8601 deadline for resolution (7 days from filing) |
createdAt | string | ISO-8601 creation timestamp |
Error Responses
| Status | Code | Description |
|---|---|---|
| 400 | BAD_REQUEST | Missing required fields (dataPrincipalId, type, description) |
| 401 | UNAUTHORIZED | Invalid or missing API key |