Erasure

These calls need the erasures:write scope. Ask for it when your key is created. Send the person’s LinkedIn URL or id:

curl -X POST https://api.clustr-ai.com/api/org/v1/erasures \
  -H "Authorization: Bearer $CLUSTR_ORG_KEY" \
  -H "Idempotency-Key: erase-jane-2026-10" \
  -H "Content-Type: application/json" \
  -d '{ "linkedin_url": "https://www.linkedin.com/in/jane-doe", "gdpr_subject": false }'

The answer is 202 with the erasure. It runs in the background.

Call	What it does
`POST /api/org/v1/erasures`	Request an erasure. Give `linkedin_url` or `person_id`.
`GET /api/org/v1/erasures/{erasureID}`	Status: `pending`, `running`, `done` or `failed`, and what was deleted in each workspace.
`GET /api/org/v1/erasures`	Your recent erasures. `limit` defaults to 50.

What is removed

In each workspace of the organization, Clustr deletes the person’s paths (as prospect or connector), engagement links, notes and workspace prospects. Your CRM data stays as it is. Each workspace’s connected warehouses are updated right away. The audit log gets one entry per workspace. When the erasure is done, a person.erased webhook is sent.

Asking twice

Asking again for a person whose erasure is still running returns that erasure (200). So does repeating an Idempotency-Key. Set gdpr_subject to true only when this is the person’s own GDPR erasure request. Their profile, experience and education are then erased from Clustr entirely. Without it, only your organization’s data about them is removed.

In MCP

Organization admins have org_erase_person, org_get_erasure and org_list_erasures.

Guides

Organization API

Endpoints

What is removed

Asking twice

In MCP

​What is removed

​Asking twice

​GDPR requests

​In MCP

What is removed

Asking twice

GDPR requests

In MCP