Users

Delete user data

Submit a deletion request for a user’s personalized data. This endpoint permanently removes the user’s stored profile, events, documents, and embeddings from Fastino’s personalization system.

POST /delete

Purpose

Use this endpoint when a user requests their data to be deleted or when you need to clear personalization state for testing, compliance, or workspace resets.
The deletion is asynchronous — a deletion ticket is created, and Fastino processes it in the background.

Endpoint

Headers

Request Body

Field	Type	Required	Description
`user_id`	string	Yes	Unique ID of the user whose data should be deleted.
`scope`	string	Optional	Determines the deletion scope (`global` by default).
`reason`	string	Optional	Optional string describing why the deletion was requested (e.g., `user_request`, `compliance`, or `test_reset`).

Example Request

{
  "user_id": "usr_42af7c",
  "scope": "global",
  "reason": "user_request"
}

Example cURL

curl -X POST "https://api.fastino.ai/delete" \
  -H "Authorization: x-api-key: sk_test_123" \
  -H "Content-Type: application/json" \
  -d '{
    "user_id": "usr_42af7c",
    "scope": "global",
    "reason": "user_request"
  }'

Example Response

{
  "ticket_id": "del_3f91",
  "status": "pending",
  "eta": "2025-10-12T16:05:00Z"
}

This confirms that the deletion request was accepted.
The ticket’s status will change to completed once processing is finished.

Response Fields

Field	Type	Description
`ticket_id`	string	Unique identifier for the deletion job.
`status`	string	Current deletion status (`pending`, `completed`, or `failed`).
`eta`	string	Estimated time of completion in ISO 8601 UTC.

Behavior

Deletion requests are asynchronous and processed in the background.
Once complete, all associated user data — profile traits, events, documents, and embeddings — are permanently removed.
A deletion cannot be undone.
Deletion tickets expire automatically after confirmation.

Error Responses

HTTP Code	Error Code	Description
`400`	`INVALID_REQUEST`	Missing or malformed parameters.
`401`	`UNAUTHORIZED`	Missing or invalid API key.
`404`	`USER_NOT_FOUND`	The specified `user_id` doesn’t exist in your workspace.
`500`	`SERVER_ERROR`	Internal system error. Retry with exponential backoff.

Example:

{
  "error": {
    "code": "USER_NOT_FOUND",
    "message": "No user found with ID usr_42af7c"
  }
}

Best Practices

Always confirm user identity before submitting a data deletion request.
Use scope=global to ensure the user’s memory is completely removed across all integrations.
For compliance automation, log ticket_id and eta for audit trails.
Avoid chaining deletions — wait for one ticket to complete before re-submitting for the same user.

Related Endpoints

Endpoint	Description
PUT `/register`	Create or update a user.
POST `/ingest`	Ingest new user data and events.
GET `/summary`	Retrieve an existing user’s deterministic summary.

Summary:
Use POST /delete to remove a user’s personalization data from Fastino.
The deletion job is processed asynchronously, ensuring privacy, compliance, and clean resets for both production and sandbox environments.

Ingest user data

Join our Discord Community

On this page

Title