Skip to content

Unassign Tag POST ​

Removes a contact from a tag, undoing Assign Tag.

Authorization ​

API Key (Authentication) — send the header Authorization: Bearer <API_KEY> (API keys start with smsk_)

HTTP Request ​

http
POST https://public-api.smsup-plus.com/Tag/deletePersonTag

Content Type ​

application/json

Parameter Description ​

PropertyTypeRequiredDescription
personIdstringRequiredContact ID (must belong to your account and not be deleted)
tagIdstringRequiredID of the tag to unassign

Response Description ​

PropertyTypeDescription
statusnumber200 on success
descriptionstringTag unassigned.

Request Example ​

bash
curl -X POST 'https://public-api.smsup-plus.com/Tag/deletePersonTag' \
  -H 'Authorization: Bearer <API_KEY>' \
  -H 'Content-Type: application/json' \
  -d '{
    "personId": "3f8b2c1e-7a4d-4e9b-9c2f-1d5e6a7b8c90",
    "tagId": "a1c2e3f4-5b6d-4e7f-8a9b-0c1d2e3f4a5b"
  }'
js
const res = await fetch('https://public-api.smsup-plus.com/Tag/deletePersonTag', {
  method: 'POST',
  headers: { Authorization: 'Bearer <API_KEY>', 'Content-Type': 'application/json' },
  body: JSON.stringify({
    personId: '3f8b2c1e-7a4d-4e9b-9c2f-1d5e6a7b8c90',
    tagId: 'a1c2e3f4-5b6d-4e7f-8a9b-0c1d2e3f4a5b',
  }),
})
console.log(await res.json())

Response Example ​

json
{
  "status": 200,
  "description": "Tag unassigned."
}

Possible Errors ​

HTTPResponseCause
200{"status":400,"description":"personId and tagId are required."}personId or tagId missing, or body is not JSON
200{"status":404,"description":"Person not found."}Contact does not exist, was deleted, or belongs to another account
200{"status":500,"description":"Failed to unassign tag."}Unassign failed — retry
401{"error":"invalid api key"}Invalid API key — see Errors

WARNING

Once authenticated, this endpoint always answers HTTP 200. Check the status field in the body.

INFO

The response is Tag unassigned. even if the pair was never assigned (the tagId itself is not checked). Each call removes one assignment.