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

Documentation for Files API

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

This API exposes 7 operations across 6 paths, and defines 9 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 6 paths 9 schemas 1 DELETE1 GET3 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 Medias 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.

Paths & Operations 7

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

Medias 7

Documentation for Files API

GET
/medias/files
Get List of Files/ Folders
fetch-media-content 11 params → 200
POST
/medias/upload-file
Upload File into Media Storage
upload-media-content 1 param body → 200
DELETE
/medias/{id}
Delete File or Folder
delete-media-content 4 params → 200
POST
/medias/{id}
Update File/ Folder
update-media-object 2 params body → 200
POST
/medias/folder
Create Folder
create-media-folder 1 param body → 200
PUT
/medias/update-files
Bulk Update Files/ Folders
bulk-update-media-objects 1 param body → 200
PUT
/medias/delete-files
Bulk Delete / Trash Files or Folders
bulk-delete-media-objects 1 param body → 200

Schemas 9

The contract defines 9 schemas that model the data the API accepts and returns. The most detailed are FolderDTO (16 properties), DeleteMediaObjectsBodyParams (4 properties), CreateFolderParams (4 properties), UpdateObject (3 properties). Each schema is shown below with its type and property counts.

UpdateMediaObject
object
2 properties 1 required
UpdateObject
object
3 properties 3 required
DeleteMediaObjectsBodyParams
object
4 properties 4 required
CreateFolderParams
object
4 properties 3 required
UpdateMediaObjects
object
3 properties 3 required
GetFilesResponseDTO
object
1 property 1 required
UploadFileResponseDTO
object
2 properties 2 required
DeleteMediaObjectItem
object
1 property 1 required
FolderDTO
object
16 properties 4 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

highlevel-medias-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 Medias 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.