Remove Tags

Remove one or more tags from a contact. Use it to keep Splashify Pro segments in sync when a contact leaves a lifecycle stage, churns, or no longer qualifies for a campaign.

Tags the contact doesn’t have are ignored — only the supplied tags that exist are removed.

Endpoint


POST https://api.splashifypro.com/api/v1/public/contacts/tags/remove

Headers

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",
  "tags": ["vip"]
}

Field	Required	Notes
`phone_number`	one of	Customer’s phone in country-code + number format (no `+`).
`contact_id`	one of	The contact’s UUID. Takes precedence over `phone_number`
`tags`	yes	Array of tag strings to remove

Example


curl -X POST https://api.splashifypro.com/api/v1/public/contacts/tags/remove \
  -H "Authorization: Basic YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "phone_number": "919876543210",
    "tags": ["vip"]
  }'

Successful response — `200 OK`


{
  "result": true,
  "message": "Tags removed successfully",
  "tags": ["lead", "website", "renewed"]
}

tags is the contact’s remaining tag list after the removal.

Error response — `404 Not Found`


{
  "result": false,
  "message": "Contact not found"
}

Status codes

Code	Meaning
`200 OK`	Tags removed
`400 Bad Request`	`tags` missing/empty, or no valid contact identifier
`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

Idempotent — removing a tag the contact doesn’t have is a no-op, and the response still returns the current list.
Tag changes sync to the contact’s open conversation in real time.