Skip to main content
DELETE
cURL

Authorizations

Authorization
string
header
required

A key generated from Settings → Developers, sent as Authorization: Bearer dr_live_<12 hex chars>_<64 hex chars>. Keys carry explicit scopes — each endpoint states the one it requires. The full key is shown exactly once at generation time and cannot be retrieved again; only the keyId prefix is shown afterward. A revoked key fails auth on its very next request.

Path Parameters

contactId
string<uuid>
required

The contact's id.

tagName
string
required

The name of one of your existing tags (1-50 characters), URL-encoded. Tag names are matched exactly; if there is no exact match, the NFC-normalized form is tried. There is no trimming and no case folding, so VIP and vip are different tags, and so are vip and vip (trailing space).

Encode spaces and non-ASCII characters (for example %EB%AF%B8%EA%B5%AC%EB%A7%A4 for 미구매), and encode % as %25, ? as %3F and # as %23.

Tag names containing / are not supported by this endpoint: depending on the hosting layer, such a name may not reach it at all. The same goes for a name that is exactly . or .. (URL clients treat those as path navigation). Such a tag can still be managed in the dashboard.

Required string length: 1 - 50

Response

The tag is not on the contact. Also returned when it was not there to begin with.

contactId
string<uuid>
required

The contact the call was about.

tag
object
required

The tag the call was about.

tagged
boolean
required

Whether the contact has the tag after the call. true for PUT, false for DELETE.