Skip to main content
Userpilot supports data deletion to comply with the right to be forgotten under GDPR. Under this right, a user can request to delete all their data. Userpilot supports this right for all users, not just those in Europe. You can use the Deletion APIs to schedule a job to delete user or company data.

ā€‹
Authorization

Userpilot API uses API tokens to authenticate requests. You can view your API key in the Environment Page. Authentication Method: Include your API key in the Authorization header:
All API requests must be made over HTTPS.
Your API key carries many privileges, so be sure to keep them secure! Do not share your secret API keys in publicly accessible areas.

ā€‹
Version

You must send the API version in the headers:

ā€‹
Endpoints

For most users, the HTTP API endpoint URL is https://analytex.userpilot.io as the examples show. If you are on Enterprise or EU hosting, refer to the Environment Page in the application to retrieve your dedicated endpoint.

ā€‹
1. Delete Users

Endpoint:
The endpoint URL uses the analytex environment. For EU data residency, use analytex-eu instead. See Environment Settings for your specific endpoint.
Headers: Request Body: Example Request:

ā€‹
2. Delete Companies

Endpoint:
The endpoint URL uses the analytex environment. For EU data residency, use analytex-eu instead. See Environment Settings for your specific endpoint.
Headers: Request Body: Example Request:

ā€‹
Response

A successful request will schedule your delete job and return a 202 Accepted status with a message indicating how many users or companies have been scheduled for deletion. Example Response:
Deletions are scheduled to be executed every 24 hours (daily at 2:00 AM UTC).

ā€‹
Rate Limits

The Delete API has the following rate limit:
  • Delete Operations: 1 request every 2 seconds for delete operations
If you exceed the rate limit, the API will return a 429 Too Many Requests error.
Best Practice: Implement exponential backoff and retry logic to handle rate limit errors gracefully.