Skip to main content
POST/api/public/v1/tags/{id}/delete

tags.delete

Delete a tag; profiles keep everything else and only lose this label.

Capability: profile.organizeCommand (idempotent)DestructiveMCP tool: tags_delete
View as Markdown

Parameters

NameTypeRequiredDescription
idpathstring (uuid)YesTag id
command_idbodystring (uuid)YesClient-generated UUID for this command. Send the same id (and body) again to get the stored receipt instead of a second change; a different body under the same id is CONFLICT.

Examples

curl -X POST "https://browlix.com/api/public/v1/tags/<id>/delete" \
  -H "Authorization: Bearer $BROWLIX_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"command_id":"<uuid>"}'

Response

201 with { data, replayed: false, correlation_id } the first time; 200 with replayed: true when the same command_id and body come again.

FieldTypeAlways presentDescription
dataobjectYes
data.tag_idstring (uuid)Yes
data.untagged_profilesintegerYesProfiles that carried this tag (min -9007199254740991, max 9007199254740991)
correlation_idstring (uuid)Yes
replayedbooleanNotrue when this command_id was already applied and the stored receipt came back

New fields can appear at any time; ignore the ones you do not know.

Errors

CodeHTTPRetryable
UNAUTHENTICATED401No
FORBIDDEN403No
RATE_LIMITED429Yes
VALIDATION_FAILED422No
NOT_FOUND404No
CONFLICT409No
OUTCOME_UNKNOWN202Yes
DEPENDENCY_UNAVAILABLE503Yes
UNKNOWN500No

Every error code and when to retry

All operations