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
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
HighLevel

HighLevel Sub-Account (Formerly Location) API

Documentation for Sub-Account (Formerly location) API

Documentation Provider Profile APIs.io OpenAPI GitHub

HighLevel Sub-Account (Formerly Location) 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 Sub-Account (Formerly Location). The published artifact set on APIs.io includes an OpenAPI specification and 60 JSON Schemas.

This API exposes 4 operations across 2 paths, and defines 13 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.

4 operations 2 paths 13 schemas 1 DELETE1 GET1 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
Resource Areas
1

Authentication & Security 4

HighLevel Sub-Account (Formerly Location) 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 4

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

Sub-Account (Formerly Location) 4

Documentation for Sub-Account (Formerly location) API

GET
/locations/{locationId}
Get Sub-Account (Formerly Location)
get-location 2 params → 200400401422
PUT
/locations/{locationId}
Put Sub-Account (Formerly Location)
put-location 2 params body → 200400401
DELETE
/locations/{locationId}
Delete Sub-Account (Formerly Location)
delete-location 3 params → 200400401
POST
/locations/
Create Sub-Account (Formerly Location)
create-location 1 param body → 200400401

Schemas 13

The contract defines 13 schemas that model the data the API accepts and returns. The most detailed are GetLocationByIdSchema (20 properties), UpdateLocationDto (16 properties), CreateLocationDto (16 properties), CreateLocationSuccessfulResponseDto (15 properties). Each schema is shown below with its type and property counts.

TwilioSchema
object
2 properties 2 required
CreateLocationSuccessfulResponseDto
object
15 properties
UpdateLocationDto
object
16 properties 1 required
SocialSchema
object
11 properties
LocationDeletedSuccessfulResponseDto
object
2 properties 2 required
ProspectInfoDto
object
3 properties 3 required
BusinessSchema
object
9 properties
SnapshotPutSchema
object
2 properties 1 required
GetLocationByIdSuccessfulResponseDto
object
1 property
GetLocationByIdSchema
object
20 properties
CreateLocationDto
object
16 properties 2 required
MailgunSchema
object
2 properties 2 required
SettingsSchema
object
4 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

highlevel-sub-account-formerly-location-api-openapi.yml Raw ↑

Other APIs HighLevel publishes across the network.

HighLevel Account API
AE Profile APIs.io
HighLevel Actions API
AE Profile APIs.io
HighLevel Affiliates API
AE Profile APIs.io
HighLevel Agents API
AE Profile APIs.io
HighLevel App Billing Management API
AE Profile APIs.io
HighLevel App Management API
AE Profile APIs.io
HighLevel Appointment Notes API
AE Profile APIs.io
HighLevel Appointments API
AE Profile APIs.io
HighLevel Associations API
AE Profile APIs.io
HighLevel Availability API
AE Profile APIs.io
HighLevel Blogs API
AE Profile APIs.io
HighLevel Brand Boards API
AE Profile APIs.io
#Sub-Account (Formerly Location)
← Back to H APIs
API Details
ID
highlevel:highlevel-sub-account-formerly-location-api
Base URL
https://api.gohighlevel.com
Docs
https://developers.gohighlevel.com
Provider
HighLevel
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=highlevel-sub-account-formerly-location-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/highlevel-sub-account-formerly-location-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

This is an independent, third-party profile of HighLevel Sub-Account (Formerly Location) 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.