Bulk End-User Deletion API
Bulk End-User Deletion API
The Bulk End-User Deletion API is now available. It erases all personal data associated with one or more end users across Ada’s systems, supporting compliance with data deletion requirements such as GDPR.
API endpoints
Two REST endpoints are available:
- Submit a deletion request (
POST /v2/end-users/delete): Accepts up to 1000 identifiers and returns ajob_idfor tracking. Requests are idempotent for 24 hours. - Get a deletion job (
GET /v2/jobs/{job_id}): Returns the job status and a per-identifier outcome for each submitted identifier.
Identifiers can be supplied by email, external ID, or Ada’s end-user identifiers, or matched by a stored variable. A job is accepted quickly, but erasure runs downstream across every data store, so reaching completed can take up to 30 days.
Get started
- Bulk End-User Deletion API reference for identifier types, dispositions, job lifecycle, error codes, and rate limits.
Data Export API: last_agent_id and last_agent_name on the Conversations endpoint
Data Export API: last_agent_id and last_agent_name on the Conversations endpoint
The v2 Conversations endpoint of the Data Export API now returns two additional fields on each conversation:
last_agent_id— the unique ID of the most recently assigned Agentlast_agent_name— the Agent’s name, corresponding tolast_agent_id
Both fields are the final entry of the existing agent_id and agent_name arrays (chronological by first-join). They return null when no Agent was assigned to the conversation.
See the Conversation object reference for the full schema.
Increased email footer character limit
The email footer character limit has been increased from 2000 to 2200 characters, giving more room for legal disclaimers, compliance messaging, and localized content.
Learn more in Email appearance settings.