Skip to main content
POST
/
api
/
v1
/
mpc
/
users
/
delete
{
  "delete-shares": [
    "{\"user-token-share\":\"a1b2c3d4e5f6\"}",
    "{\"user-token-share\":\"share2\"}"
  ]
}

{
  "type": "job-status",
  "job-id": "550e8400-e29b-41d4-a716-446655440000",
  "status": "created"
}

​
Overview

Permanently removes user data from the boop network by submitting encrypted delete shares for multi-party computation. This operation cannot be undone.
This endpoint permanently deletes user data and cannot be reversed. Use with extreme caution.

​
Request

​
delete-shares
array
required
Array of delete shares for MPC computation. Each share is a serialized JSON string containing the user-token-share for the user to delete.

​
Response

​
type
string
required
Will be “job-status” for async operations
​
job-id
string
required
Unique identifier for tracking the delete job
​
status
string
required
Current status: “created”, “processing”, “completed”, or “failed”
{
  "delete-shares": [
    "{\"user-token-share\":\"a1b2c3d4e5f6\"}",
    "{\"user-token-share\":\"share2\"}"
  ]
}

{
  "type": "job-status",
  "job-id": "550e8400-e29b-41d4-a716-446655440000",
  "status": "created"
}

​
Job Status Polling

After submitting a delete request, poll the job status endpoint: 
GET /api/v1/mpc/jobs/{job-id}

​
Data Deletion Compliance

This endpoint supports GDPR and other privacy regulations by providing:
  • Complete data removal: All user data is permanently deleted from MPC storage
  • Verification: Job status confirms successful deletion
  • Audit trail: Delete operations are logged for compliance

​
Security Considerations

  • All shares must be properly encrypted before transmission
  • Each share should be sent to a different MPC node
  • Implement proper authorization checks before deletion
  • Use TLS for all API communications
  • Log all delete operations for audit purposes

​
Rate Limits

  • 10 user deletions per minute per API key
  • 100 user deletions per hour per API key