Anonymize visitor data (GDPR erasure)
Anonymizes a visitor's PII (identifier, fingerprint, geo data, metadata) in compliance with GDPR Article 17.
/api/visitors/{id}/anonymizeAnonymizes a visitor's PII (identifier, fingerprint, geo data, metadata) in compliance with GDPR Article 17. Preserves the visitor row and conversation history for analytics. Also scrubs the visitor's message content, sessions/page views, survey comments, translations and analysis output, cancels queued chatbot/translation/analysis work, and schedules durable deletion of private attachments attributable to the visitor. Anonymization permanently removes or replaces identifying profile and tracking data. Read the resulting visitor before retrying after an ambiguous timeout.
Endpoint requirements
- Credentials
- Use either
Bearer API keyorX-API-Key header. - Required scope
visitors:write- Module
- Automation & API module (
api_access) - Organization and site scope
- Requests can access only resources owned by the authenticated organization. The API does not reveal whether an identifier belongs to another organization or site.
- Retry behavior
- Convergent write: Retrying leaves the resource in the same resulting state. If the first request succeeded, a later retry may return conflict or not found because the change has already taken effect.
Path Parameters
Resource identifier.
^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$uuidHeader Parameters
DA-4035: selects the active site (project) for project-scoped operations. Accepts a site UUID, or the literal all to aggregate across every accessible site on read-only aggregate routes (single-or-all-read). Mutations and single-site routes reject all. Path-owned project routes (/api/projects/{projectId}/…) resolve the site from the URL and ignore this header. Conflicting selectors across header/query/body/path return PROJECT_CONTEXT_CONFLICT (400); an archived site returns PROJECT_ARCHIVED (410).
Response Body
application/json
application/json
application/json
application/json
application/json
application/json
application/json
application/json
application/json
application/json
{ "success": true}Request examples
curl
curl --request POST \
'https://api.convor.io/api/visitors/22222222-2222-4222-8222-222222222222/anonymize' \
--header 'Accept: application/json' \
--header 'Authorization: Bearer convor_sk_...'JavaScript
const response = await fetch("https://api.convor.io/api/visitors/22222222-2222-4222-8222-222222222222/anonymize", {
method: "POST",
headers: {
"Accept": "application/json",
"Authorization": "Bearer convor_sk_..."
},
});
const contentType = response.headers.get("content-type") ?? "";
const data = response.status === 204
? null
: contentType.includes("json")
? await response.json()
: contentType.startsWith("text/")
? await response.text()
: await response.blob();
if (!response.ok) {
const message = typeof data === "object" && data !== null
&& "error" in data && typeof data.error === "object"
&& data.error !== null && "message" in data.error
? String(data.error.message)
: "Convor API request failed (" + response.status + ")";
throw new Error(message);
}
console.log(data);Was this page helpful?