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

Documentation for Ad-publishing API

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

This API exposes 28 operations across 24 paths, and defines 18 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.

28 operations 24 paths 18 schemas 5 DELETE6 GET10 POST7 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 Ads 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 28

Across 24 paths, the API surfaces 28 operations — 5 DELETE, 6 GET, 10 POST, 7 PUT. Each is listed below with its method, path, parameters, and response codes.

Facebook Ads 28

Documentation for Ad-publishing API

GET
/ad-publishing/facebook/targeting/search
Search targeting options
fb-search-targeting 4 params → 200400401422
POST
/ad-publishing/facebook/campaigns/{campaignId}/publish
Publish campaign
fb-publish-campaign 2 params body → 201400401422
GET
/ad-publishing/facebook/pixels
Get conversion pixels
fb-get-pixels 5 params → 200400401422
PUT
/ad-publishing/facebook/pixels
Upsert conversion pixel
fb-upsert-pixel 1 param body → 200400401422
GET
/ad-publishing/facebook/custom-audience
Get custom audiences
fb-get-custom-audiences 5 params → 200400401422
DELETE
/ad-publishing/facebook/custom-audience/{audienceId}
Delete custom audience
fb-delete-custom-audience 3 params → 200400401422
PUT
/ad-publishing/facebook/custom-audience/{audienceId}
Update custom audience
fb-update-custom-audience 2 params body → 200400401422
GET
/ad-publishing/facebook/custom-audience/{audienceId}
Get custom audience by ID
fb-get-custom-audience-by-id 3 params → 200400401422
PUT
/ad-publishing/facebook/custom-audience/{audienceId}/member
Add custom audience member
fb-add-custom-audience-member 2 params body → 200400401422
DELETE
/ad-publishing/facebook/custom-audience/{audienceId}/member
Remove custom audience member
fb-remove-custom-audience-member 2 params body → 200400401422
PUT
/ad-publishing/facebook/custom-audience/{audienceId}/member/batch
Batch update audience members
fb-batch-update-audience-members 2 params body → 200400401422
GET
/ad-publishing/facebook/campaign/{campaignId}
Get campaign with linked entities
fb-get-campaign 5 params → 200400401422
GET
/ad-publishing/facebook/entity
Get entities
fb-get-entity 10 params → 200400401422
PUT
/ad-publishing/facebook/campaigns
Upsert campaign
fb-upsert-campaign 1 param body → 200400401422
PUT
/ad-publishing/facebook/adsets
Upsert adset
fb-upsert-adset 1 param body → 200400401422
PUT
/ad-publishing/facebook/ads-v2
Upsert ad
fb-upsert-ad 1 param body → 200400401422
POST
/ad-publishing/facebook/campaigns/{campaignId}/pause
Pause campaign
fb-pause-campaign 2 params body → 201400401422
POST
/ad-publishing/facebook/campaigns/{campaignId}/resume
Resume campaign
fb-resume-campaign 2 params body → 201400401422
POST
/ad-publishing/facebook/campaigns/{campaignId}/duplicate
Duplicate campaign
fb-duplicate-campaign 2 params body → 201400401422
DELETE
/ad-publishing/facebook/campaigns/{campaignId}
Delete campaign
fb-delete-campaign 2 params body → 200400401422
POST
/ad-publishing/facebook/adsets/{adsetId}/pause
Pause ad set
fb-pause-adset 2 params body → 201400401422
POST
/ad-publishing/facebook/adsets/{adsetId}/resume
Resume ad set
fb-resume-adset 2 params body → 201400401422
POST
/ad-publishing/facebook/adsets/{adsetId}/duplicate
Duplicate ad set
fb-duplicate-adset 2 params → 201400401422
DELETE
/ad-publishing/facebook/adsets/{adsetId}
Delete ad set
fb-delete-adset 2 params body → 200400401422
POST
/ad-publishing/facebook/ads/{adId}/pause
Pause ad
fb-pause-ad 2 params body → 201400401422
POST
/ad-publishing/facebook/ads/{adId}/resume
Resume ad
fb-resume-ad 2 params body → 201400401422
POST
/ad-publishing/facebook/ads/{adId}/duplicate
Duplicate ad
fb-duplicate-ad 2 params → 201400401422
DELETE
/ad-publishing/facebook/ads/{adId}
Delete ad
fb-delete-ad 2 params body → 200400401422

Schemas 18

The contract defines 18 schemas that model the data the API accepts and returns. The most detailed are UpsertAdDTO (16 properties), UpsertAdsetDTO (13 properties), FacebookAudienceDTO (10 properties), MediaDTO (8 properties). Each schema is shown below with its type and property counts.

AudienceLocaleDTO
object
2 properties 2 required
UpdateCustomAudienceDTO
object
3 properties 2 required
PublishAdDTO
object
1 property 1 required
AudienceLocationGeometry
object
2 properties 2 required
UpsertConversionPixelDTO
object
5 properties 2 required
UpsertAdsetDTO
object
13 properties 2 required
FbUpdateAudienceBodyDTO
object
3 properties 3 required
FacebookAudienceDTO
object
10 properties 1 required
AudienceCustomAudienceItemDTO
object
2 properties 2 required
AudienceLocationDTO
object
7 properties 4 required
LocationIdBodyDTO
object
1 property 1 required
MediaDTO
object
8 properties 2 required
UpdateCustomAudienceBatchDTO
object
5 properties 2 required
Budget
object
4 properties 2 required
AudienceInterestDTO
object
3 properties 2 required
UpsertCampaignDTO
object
6 properties 1 required
UpsertAdDTO
object
16 properties 3 required
AudiencePlacementsDTO
object
3 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

highlevel-facebook-ads-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 Ads 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.