How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

HighLevel Contacts API

Documentation for Contacts API

HighLevel Contacts API is one of 117 APIs that HighLevel publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

This API exposes 60 JSON Schema definitions.

Tagged areas include Contacts. The published artifact set on APIs.io includes an OpenAPI specification and 60 JSON Schemas.

This API exposes 7 operations across 4 paths, and defines 27 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

Requests are made against a single base URL, https://services.leadconnectorhq.com.

7 operations 4 paths 27 schemas 1 DELETE3 GET2 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://api.gohighlevel.com
Authentication
HTTP Bearer, HTTP Bearer, HTTP Bearer, HTTP Bearer, HTTP Bearer
Resource Areas
1

Authentication & Security 5

HighLevel Contacts API declares 5 security schemes for authenticating requests. It accepts HTTP bearer tokens (JWT) (bearer). It accepts HTTP bearer tokens (JWT) (Location-Access). It accepts HTTP bearer tokens (JWT) (Location-Access-Only). It accepts HTTP bearer tokens (JWT) (Agency-Access). It accepts HTTP bearer tokens (JWT) (Agency-Access-Only).

  • bearer — Use the Access Token generated with user type as Sub-Account (OR) Private Integration Token of Sub-Account.
  • Location-Access — Use the Access Token generated with user type as Sub-Account (OR) Private Integration Token of Sub-Account.
  • Location-Access-Only — Use the Access Token generated with user type as Sub-Account.
  • Agency-Access — Use the Access Token generated with user type as Agency (OR) Private Integration Token of Agency.
  • Agency-Access-Only — Use the Access Token generated with user type as Agency.

Paths & Operations 7

Across 4 paths, the API surfaces 7 operations — 1 DELETE, 3 GET, 2 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

Contacts 7

Documentation for Contacts API

GET
/contacts/{contactId}
Get Contact
get-contact 2 params → 200400401422
PUT
/contacts/{contactId}
Update Contact
update-contact 2 params body → 200400401422
DELETE
/contacts/{contactId}
Delete Contact
delete-contact 2 params → 200400401422
POST
/contacts/upsert
Upsert Contact
upsert-contact 1 param body → 200400401422
GET
/contacts/business/{businessId}
Get Contacts By BusinessId
get-contacts-by-businessId 6 params → 200400401422
POST
/contacts/
Create Contact
create-contact 1 param body → 201400401422
GET
/contacts/deprecated
Get Contacts
get-contacts 6 params → 200400401422

Schemas 27

The contract defines 27 schemas that model the data the API accepts and returns. The most detailed are GetContectByIdSchema (37 properties), CreateContactSchema (36 properties), UpsertContactDto (24 properties), CreateContactDto (23 properties). Each schema is shown below with its type and property counts.

InboundDndSettingsSchema
object
1 property
AttributionSource
object
18 properties 1 required
NumericField
object
3 properties 1 required
ContactsByIdSuccessfulResponseDto
object
1 property
SingleSelectField
object
3 properties 1 required
CustomFieldSchema
object
2 properties
DndSettingsSchema
object
6 properties
CheckboxField
object
3 properties 1 required
UpsertContactsSuccessfulResponseDto
object
3 properties
GetContectByIdSchema
object
37 properties
CreateContactSchema
object
36 properties
UpdateContactsSuccessfulResponseDto
object
2 properties
CreateContactDto
object
23 properties 1 required
DeleteContactsSuccessfulResponseDto
object
1 property
LargeTextField
object
3 properties 1 required
FileField
object
3 properties 1 required
DndSettingSchema
object
3 properties 1 required
CreateContactsSuccessfulResponseDto
object
1 property
RadioField
object
3 properties 1 required
ContactsSearchSchema
object
12 properties
TextField
object
3 properties 1 required
ContactsSearchSuccessfulResponseDto
object
2 properties
MultiSelectField
object
3 properties 1 required
UpdateContactDto
object
20 properties
InboundDndSettingSchema
object
2 properties 1 required
UpsertContactDto
object
24 properties 1 required
MonetoryField
object
3 properties 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

highlevel-contacts-api-openapi.yml Raw ↑

Other APIs HighLevel publishes across the network.

HighLevel Account API
HighLevel Actions API
HighLevel Affiliates API
HighLevel Agents API
HighLevel App Billing Management API
HighLevel App Management API
HighLevel Appointment Notes API
HighLevel Appointments API
HighLevel Associations API
HighLevel Availability API
HighLevel Blogs API
HighLevel Brand Boards API
Where this information came from

This is an independent, third-party profile of HighLevel Contacts API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.