Skip to contentDevelopersPrezly website
Privacy requests

Confirm Privacy Request

Confirm an existing request after verifying the requester.

Personal tokens are not supported for this endpoint. Use an integration API key. Your account must also have access to the requested data. Authentication

Confirmation creates pending work for matching contacts in the newsroom’s account and triggers account notifications. It does not fulfill an export, correction, or deletion. Reconfirming an already confirmed request returns its current state.

Read the guide

POST
/newsrooms/{newsroom_id}/privacy-requests/{id}/confirm

Assumes requester verification has already happened. Confirmation creates pending contact privacy tasks for matching contacts and queues a notification. It does not itself export, correct or delete contact data. Already confirmed requests are returned without creating the work again.

Personal access tokens are not supported for this endpoint. Use an integration API key with the required permissions.

Authorization

API_key
headerAuthorizationBearer <token>

Bearer authentication using an integration API key, or a personal access token only where the operation explicitly supports it. Every listed personal-token scope is required; owner permissions and newsroom access still apply.

Path Parameters

newsroom_id*string

Newsroom UUID or ID

Length1 <= length
id*string

Privacy Request UUID

Response Body

OK

application/json
  1. response
privacy_request?
Example Request
curl -X POST 'https://api.prezly.com/v2/newsrooms/string/privacy-requests/string/confirm'
Example Response200
{  "privacy_request": {    "id": "string",    "status": "unconfirmed",    "email": "string"  }}