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 Custom Fields V2 API

Custom fields are data points that allow you to capture and store specific information tailored to your business requirements. You can create fields across field types like text, numeric, selection options and special fields like date/time or signature

HighLevel Custom Fields V2 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 Custom Fields V2. The published artifact set on APIs.io includes an OpenAPI specification and 60 JSON Schemas.

This API exposes 8 operations across 5 paths, and defines 10 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.

8 operations 5 paths 10 schemas 2 DELETE2 GET2 POST2 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
Resource Areas
1

Authentication & Security 4

HighLevel Custom Fields V2 API declares 4 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).

  • 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.

Paths & Operations 8

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

Custom Fields V2 8

Custom fields are data points that allow you to capture and store specific information tailored to your business requirements. You can create fields across field types like text,…

GET
/custom-fields/{id}
Get Custom Field / Folder By Id
get-custom-field-by-id 2 params → 200400401
PUT
/custom-fields/{id}
Update Custom Field By Id
update-custom-field 2 params body → 200400401
DELETE
/custom-fields/{id}
Delete Custom Field By Id
delete-custom-field 2 params → 200400401
GET
/custom-fields/object-key/{objectKey}
Get Custom Fields By Object Key
get-custom-fields-by-object-key 3 params → 200400401
POST
/custom-fields/folder
Create Custom Field Folder
create-custom-field-folder 1 param body → 201400401
PUT
/custom-fields/folder/{id}
Update Custom Field Folder Name
update-custom-field-folder 2 params body → 200400401
DELETE
/custom-fields/folder/{id}
Delete Custom Field Folder
delete-custom-field-folder 3 params → 200400401
POST
/custom-fields/
Create Custom Field
create-custom-field 1 param body → 201400401

Schemas 10

The contract defines 10 schemas that model the data the API accepts and returns. The most detailed are ICustomField (16 properties), CreateCustomFieldsDTO (13 properties), UpdateCustomFieldsDTO (8 properties), ICustomFieldFolder (4 properties). Each schema is shown below with its type and property counts.

CreateCustomFieldsDTO
object
13 properties 6 required
UpdateFolder
object
2 properties 2 required
ICustomFieldFolder
object
4 properties 4 required
CustomFieldsResponseDTO
object
2 properties
ICustomField
object
16 properties 9 required
UpdateCustomFieldsDTO
object
8 properties 2 required
CustomFolderDeleteResponseDto
object
3 properties 3 required
OptionDTO
object
3 properties 2 required
CreateFolder
object
3 properties 3 required
CustomFieldSuccessfulResponseDto
object
1 property

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

highlevel-custom-fields-v2-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 Custom Fields V2 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.