List erasures
GET
/erasures
const url = 'https://example.com/erasures';const options = { method: 'GET', headers: {cookie: 'bottle.session_token=<bottle.session_token>'}};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request GET \ --url https://example.com/erasures \ --cookie bottle.session_token=<bottle.session_token>Kept after the details themselves are gone, because proving an erasure happened is the other half of carrying it out. Holds no personal data: an id, a reason, a date, and how much moved.
Authorizations
Section titled “Authorizations”Responses
Section titled “Responses”The record
Media typeapplication/json
object
items
required
Array<object>
object
id
required
UUID v7
string format: uuid
subject
required
string
subjectId
required
string
reason
required
string
requestedBy
required
string | null
addressesErased
required
integer
ordersKept
required
integer
ordersDeleted
required
integer
subjectDeleted
required
boolean
createdAt
required
string format: date-time
Example
{ "items": [ { "id": "019205d1-6e7a-7c3b-9f6e-3a2b1c0d9e8f", "subject": "customer", "reason": "request" } ]}Not signed in
Media typeapplication/json
object
error
required
string
message
required
string
Example
{ "error": "not_found", "message": "Customer not found"}Not a member, or without the permission this needs
Media typeapplication/json
object
error
required
string
message
required
string
Example
{ "error": "not_found", "message": "Customer not found"}Validation failed
Media typeapplication/json
object
error
required
string
message
required
string
issues
required
Array<object>
object
path
required
string
message
required
string
Example
{ "error": "validation", "issues": [ { "path": "email", "message": "Invalid email" } ]}