GoHighLevel Contacts API

Remove Tags

DELETE/contacts/:contactId/tags

DELETE /contacts/:contactId/tags Remove one or more tags from a contact. Removing a tag can also be what takes a contact out of a tag-triggered workflow. It takes 1 path parameter and 1 body field, requires the contacts.write scope and authenticates with a sub-account (location) token.

Request and authentication

Method: DELETE
Full URL: https://services.leadconnectorhq.com/contacts/:contactId/tags
Scopes: contacts.write
Token type: Sub-account (location) token
Accepted auth: OAuth Access Token, Private Integration Token
API version header: Version: 2021-07-28
Schema verified: 22 June 2026

This endpoint is safe to fan out in parallel, so a batch of records costs roughly one round trip instead of one per record. Hylo's bulk tools do that server-side and retry HighLevel's 429s with back-off.

Path parameters

Substituted into the URL. Required by definition.

Name	Type	Description
`contactId`required	`string`	Example: `sx6wyHhbFdRXh302LLNR`

Request body

JSON body fields. Nested objects are shown indented under their parent.

Name	Type	Description
`tags`required	`array`	Example: `minim,velit magna`

Response fields

Top-level fields returned on a successful call.

Name	Type	Description
`tags`	`array`	Example: `minim,velit magna`

Example request

Copy-paste ready. Swap YOUR_TOKEN for your access token or Private Integration Token, and the sample ID for your own.

curl -X DELETE 'https://services.leadconnectorhq.com/contacts/sx6wyHhbFdRXh302LLNR/tags' \
  -H 'Authorization: Bearer YOUR_TOKEN' \
  -H 'Version: 2021-07-28'

Skip the schema lookup

Hylo gives your AI agent this schema — and the other 52 documented here — without you looking anything up. Ask in plain English; it picks the endpoint, fills the body, and can run the call against your own sub-account.

View pricing Read the setup guide

More contacts endpoints