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 Facebook Integration API

Documentation for Ad-publishing API

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

This API exposes 16 operations across 11 paths, and defines 12 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.

16 operations 11 paths 12 schemas 3 DELETE9 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 Facebook Integration 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 16

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

Facebook Integration 16

Documentation for Ad-publishing API

GET
/ad-publishing/facebook/me
Get current Facebook user
fb-get-current-user 2 params → 200400401422
GET
/ad-publishing/facebook/pages
Get Facebook pages
fb-get-pages 3 params → 200400401422
GET
/ad-publishing/facebook/page/{pageId}/instagram
Get Instagram accounts for page
fb-get-instagram-accounts 4 params → 200400401422
GET
/ad-publishing/facebook/page/{pageId}/forms
Get page lead forms
fb-get-page-lead-forms 3 params → 200400401422
POST
/ad-publishing/facebook/page/{pageId}/forms
Create page lead form
fb-create-page-lead-form 2 params body → 201400401422
GET
/ad-publishing/facebook/ad-accounts
Get ad accounts
fb-get-ad-accounts 6 params → 200400401422
GET
/ad-publishing/facebook/ad-accounts/{adAccountId}
Get ad account details
fb-get-ad-account 3 params → 200400401422
DELETE
/ad-publishing/facebook/ad-accounts/{adAccountId}
Delete ad account
fb-delete-ad-account 2 params body → 200400401422
GET
/ad-publishing/facebook/conversation-forms
Get conversation forms
fb-get-conversation-forms 2 params → 200400401422
POST
/ad-publishing/facebook/conversation-forms
Create conversation form
fb-create-conversation-form 1 param body → 201400401422
POST
/ad-publishing/facebook/integration
Create Facebook integration
fb-create-integration 1 param body → 201400401422
GET
/ad-publishing/facebook/integration
Get Facebook integration
fb-get-integration 2 params → 200400401422
DELETE
/ad-publishing/facebook/integration
Delete Facebook integration
fb-delete-integration 1 param body → 200400401422
DELETE
/ad-publishing/facebook/page
Delete page connection
fb-delete-page 3 params → 200400401422
PUT
/ad-publishing/facebook/page/default
Set default page
fb-set-default-page 2 params body → 200400401422
GET
/ad-publishing/facebook/lead-form/{leadFormId}
Get lead form by ID
fb-get-lead-form 3 params → 200400401422

Schemas 12

The contract defines 12 schemas that model the data the API accepts and returns. The most detailed are CreateLeadFormDTO (10 properties), ThankYouPage (7 properties), CreateConversationFormDTO (4 properties), FormQuestion (4 properties). Each schema is shown below with its type and property counts.

FbSetDefaultPageBodyDTO
object
1 property 1 required
CreateConversationFormDTO
object
4 properties 4 required
CustomDisclaimer
object
3 properties 2 required
FormQuestionOption
object
2 properties 2 required
WelcomeMessageQuestion
object
2 properties 1 required
CustomDisclaimerCheckbox
object
3 properties 3 required
CreateLeadFormDTO
object
10 properties 6 required
LocationIdBodyDTO
object
1 property 1 required
GreetingCard
object
3 properties 3 required
CreateIntegrationDTO
object
3 properties 2 required
FormQuestion
object
4 properties 2 required
ThankYouPage
object
7 properties 4 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

highlevel-facebook-integration-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 Facebook Integration 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.