Delete Contact
Permanently delete a contact from your Splashify Pro workspace, along with its conversations and message history. Useful for honouring data-deletion / GDPR / DPDP requests from your own system.
Warning: This is a hard delete — the contact, its conversations, and its messages are removed and cannot be restored. To temporarily hide a contact instead, archive it from the app UI.
Endpoint
POST https://api.splashifypro.com/api/v1/public/contacts/deleteHeaders
| Header | Value |
|---|---|
Authorization | Basic YOUR_API_KEY |
Content-Type | application/json |
Request body
Identify the contact by either phone_number or contact_id.
{
"phone_number": "919876543210"
}| Field | Required | Notes |
|---|---|---|
phone_number | one of | Customer’s phone in country-code + number format (no +). |
contact_id | one of | The contact’s UUID (as returned by Create Contact / Get Users). Takes precedence over phone_number |
Example
curl -X POST https://api.splashifypro.com/api/v1/public/contacts/delete \
-H "Authorization: Basic YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{ "phone_number": "919876543210" }'Successful response — 200 OK
{
"result": true,
"message": "Contact deleted successfully"
}Error response — 404 Not Found
{
"result": false,
"message": "Contact not found"
}Status codes
| Code | Meaning |
|---|---|
200 OK | Contact deleted |
400 Bad Request | Neither phone_number nor a valid contact_id supplied |
401 Unauthorized | API key invalid or missing |
404 Not Found | No active contact matches the identifier |
429 Too Many Requests | Rate limit exceeded |
Implementation tips
- Idempotency — a second delete for the same contact returns
404. Treat404as “already deleted” rather than an error in cleanup jobs. - Prefer
contact_idwhen you have it — it’s a direct lookup and avoids any ambiguity when two contacts share a number across channels.