GoHighLevel Contacts API

Remove Followers Contact

DELETE/contacts/:contactId/followers

DELETE /contacts/:contactId/followers Remove one or more followers from a contact, stopping their notifications about activity on that contact. 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/followers
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

Path parameters

Substituted into the URL. Required by definition.

NameTypeDescription
contactIdrequiredstring

Example: sx6wyHhbFdRXh302Lunr

Request body

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

NameTypeDescription
followersrequiredarray

Example: sx6wyHhbFdRXh302Lunr,sx6wyHhbFdRXh302Lunr

Response fields

Top-level fields returned on a successful call.

NameTypeDescription
followersarray

Example: sx6wyHhbFdRXh302Lunr,sx6wyHhbFdRXh302LLss

followersRemovedarray

Example: Mx6wyHhbFdRXh302Luer,Ka6wyHhbFdRXh302LLsAm

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/sx6wyHhbFdRXh302Lunr/followers' \
  -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.

More contacts endpoints