Data Subject Requests

We currently support two data subject request types access & erasure .

Access will let you determine if you have stored that data subjects identity anywhere in Poplar (&/or Share Local Media if you are also a SLM Solo, Shared or Insert client).

Erasure will submit an erasure (deletion) request for a data subject's identity within your account. This will scan across mailings, orders, and audiences. Note: that erasure requests do not apply within your opt out list. When you submit an erasure request we will also automatically add the data subject identity to your opt out list to prevent them from being mailed by you in the future.

Create Data Subject Request

POST https://api.heypoplar.com/v1/dsr/request

Use this endpoint to create a data subject request for one or more subject identities.

Headers

Request Body

{
    // Response
}

Subject Identity Objects

A subject data request requires an array of subject identity objects. A request can contain multiple subject identity objects but all subject identities should be for the same user. For example, a data subject request may contain a subject identity object for a user's email and one for their address.

Subject identity objects should contain the following fields:

The identity_value object for address request should contain the following fields:

Fetch Data Subject Request Status

GET https://api.heypoplar.com/v1/dsr/request/:subject_request_id

This endpoint allows you to query the status of a data subject request.

Path Parameters

{
  "controller_id": "87f42076-3bcc-4e93-a72a-a0703746ec98",
  "subject_request_id": "e93693d5-5d99-4c45-8993-b31684426a38",
  "request_status": "completed",
  "result": "deleted",
}

Last updated