---
title: "Create Dsar Request"
method: POST
path: "/v2/dsar/requests"
tags: ["GDPR"]
---

# Create Dsar Request

`POST /v2/dsar/requests`

### Create Data Subject Access Request

Initiates a new Data Subject Access Request (DSAR). A verification token is
generated and should be sent to the customer via email for identity verification.
The request includes a 30-day response deadline per GDPR Article 12.

**Request Body**:
- `customerId`: UUID of the customer requesting access
- `requestType`: Type of request (access, deletion, portability, rectification)
- `requestedBy`: Email address of the person making the request

**Returns**:
- 201 Created with the DSAR request details including deadline.

## Headers

- `authorization` string, nullable

## Request body

- CreateDSARRequestPayload — Payload for creating a new DSAR request.
  - `customerId` string, required
  - `requestType` 'access' | 'deletion' | 'portability' | 'rectification' — Type of Data Subject Access Request.
  - `requestedBy` string, required

## Response `201`

Successful Response

- DSARRequestResponse — Response containing DSAR request details.
  - `id` string, required
  - `status` 'pending' | 'processing' | 'completed' | 'failed' | 'denied', required — Status of DSAR request processing.
  - `deadline` string, date-time, required
  - `createdAt` string, date-time, required

## Other responses

- `422` — Validation Error

---

[API](https://skmtc.net/loyalty/apis/loyaltydog.md) · [All operations](https://skmtc.net/loyalty/apis/loyaltydog/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/loyalty/loyaltydog/versions/42b7b22af2b6/schema)