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 Products API

Documentation for products API

HighLevel Products 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 Product. 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 26 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 26 schemas 1 DELETE2 GET3 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 Products 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, 2 GET, 3 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

Products 7

Documentation for products API

POST
/products/bulk-update
Bulk Update Products
bulkUpdate 1 param body → 201400401422
POST
/products/bulk-update/edit
Bulk Edit Products and Prices
bulkEdit 1 param body → 201400401422
GET
/products/{productId}
Get Product by ID
get-product-by-id 4 params → 200400401422
DELETE
/products/{productId}
Delete Product by ID
delete-product-by-id 4 params → 200400401422
PUT
/products/{productId}
Update Product by ID
update-product-by-id 2 params body → 200400401422
POST
/products/
Create Product
create-product 1 param body → 201400401422
GET
/products/
List Products
list-invoices 13 params → 200400401422

Schemas 26

The contract defines 26 schemas that model the data the API accepts and returns. The most detailed are UpdateProductDto (19 properties), CreateProductDto (18 properties), UpdateProductResponseDto (17 properties), CreateProductResponseDto (17 properties). Each schema is shown below with its type and property counts.

BulkEditProductDto
object
16 properties 1 required
GetProductResponseDto
object
17 properties 6 required
CreateProductResponseDto
object
17 properties 6 required
ListProductsResponseDto
object
2 properties 2 required
PriceDimensionsDto
object
4 properties 4 required
BulkUpdateDto
object
10 properties 4 required
ProductSEODto
object
2 properties
ListProductsStats
object
1 property 1 required
ProductVariantOptionDto
object
2 properties 2 required
DefaultProductResponseDto
object
17 properties 6 required
ProductVariantDto
object
3 properties 3 required
PriceUpdateField
object
3 properties 2 required
UpdateProductResponseDto
object
17 properties 6 required
DeleteProductResponseDto
object
1 property 1 required
ShippingOptionsDto
object
2 properties
WeightOptionsDto
object
2 properties 2 required
BulkEditPriceDto
object
14 properties 1 required
BulkUpdateResponseDto
object
2 properties 1 required
CreateProductDto
object
18 properties 3 required
BulkUpdateFilters
object
4 properties
BulkEditRequestDto
object
3 properties 3 required
BulkEditResponseDto
object
3 properties 3 required
ProductLabelDto
object
3 properties 1 required
UpdateProductDto
object
19 properties 3 required
ProductMediaDto
object
6 properties 3 required
RecurringDto
object
2 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

highlevel-products-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 Products 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.