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 Recurring Tasks API

Documentation for Sub-Account (Formerly location) API

HighLevel Recurring Tasks 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 Recurring Tasks. 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 6 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 6 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 Recurring Tasks 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.

Recurring Tasks 4

Documentation for Sub-Account (Formerly location) API

GET
/locations/{locationId}/recurring-tasks/{id}
Get Recurring Task By Id
get-recurring-task-by-id 3 params → 200400401
PUT
/locations/{locationId}/recurring-tasks/{id}
Update Recurring Task
update-recurring-task 3 params body → 200400401
DELETE
/locations/{locationId}/recurring-tasks/{id}
Delete Recurring Task
delete-recurring-task 3 params → 200400401
POST
/locations/{locationId}/recurring-tasks
Create Recurring Task
create-recurring-task 2 params body → 201400401

Schemas 6

The contract defines 6 schemas that model the data the API accepts and returns. The most detailed are RecurringTaskResponseDTO (11 properties), CustomRRulesOptions (10 properties), RecurringTaskCreateDTO (6 properties), RecurringTaskUpdateDTO (6 properties). Each schema is shown below with its type and property counts.

CustomRRulesOptions
object
10 properties 4 required
RecurringTaskUpdateDTO
object
6 properties
RecurringTaskSingleResponseDTO
object
1 property 1 required
RecurringTaskCreateDTO
object
6 properties 2 required
DeleteRecurringTaskResponseDTO
object
2 properties 2 required
RecurringTaskResponseDTO
object
11 properties 9 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

highlevel-recurring-tasks-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 Recurring Tasks 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.