New aggregated insights just released Learn more →

Privacy erasure request (DSAR) API

Request deletion for a user identifier in Trace

Written by Trace Team Updated 14-04-26

Who this is for

Developers and privacy operators handling data subject erasure requests.

Endpoint overview

  • Endpoint: POST /v1/privacy/request
  • Auth: x-trace-api-key
  • Purpose: request deletion workflow for supported identifiers.

Request format guidance

  • Include the identifier type and value exactly as required by your implementation.
  • Use validated values only (for example hashed identity token format where applicable).
  • Scope the request to the correct site/workspace API key.

Operational checklist

  1. Validate identifier source and ownership.
  2. Submit request via server-side call.
  3. Log request timestamp and internal case reference.
  4. Confirm deletion status in your internal DSAR workflow.

Troubleshooting

  • Invalid identifier error: check format and hashing expectations.
  • Unauthorized response: verify x-trace-api-key scope and environment.
  • No observable change: allow processing window, then retry with confirmed identifier.

Still need help?

Contact our support team and we will get back to you as soon as we can.

support@usetrace.io