Access the official GHL Customer Care API documentation. Learn about authentication methods, rate limits, available endpoints, OAuth setup, and developer resources.
7 min read1,492 words3 explained imagesUpdated Tue, 18 Aug at 7:48 AM
Assistants need to reach this page over the internet. While it is only running on your machine, these two buttons will not be able to load it.
Each image has a one line explanation. Switch to full detail for the step it belongs to, the fields and buttons involved, examples and the whole procedure.
GHL Customer Care provides a comprehensive API platform that enables developers to build integrations, automations, and custom applications with the GHL Customer Care CRM and Marketplace. Our API includes REST endpoints for contacts, messaging, workflows, calendars, payments, webhooks, and more.
IMPORTANT: V1 APIs has reached end-of-support as on 31-December-2025. All API Documentation - https://marketplace.https://ghlcustomercare.com/docs/
Existing connections/integrations will continue to work, however no support or updates will be provided for V1 APIs.
Want to migrate from V1 to V2? (with a ton of new functionalities and security features)
Check out - Private IntegrationsPlease Note: Older API documentation versions remain accessible for reference. This allows developers to continue supporting existing integrations while reviewing newer API versions when they are ready to upgrade.Figure 1What this shows GHL Customer Care provides a comprehensive API platform that enables developers to build integrations, automations, and custom applications…What this showsIllustrates "GHL Customer Care API Documentation".This screenshot appears in "GHL Customer Care API Documentation". The text alongside this image reads: GHL Customer Care provides a comprehensive API platform that enables developers to build integrations, automations, and custom applications with the GHL Customer Care CRM and Marketplace. Our API includes REST endpoints for contacts, messaging, workflows, calendars, payments, webhooks, and more. This part of the guide covers 7 fields, listed below. Immediately after, the guide continues: Please Note: Going forward, the ability to generate new API keys will be removed from both Agency and Sub-account settings.This change applies to accounts that have not yet generated or are not currently using a API key.Image 1 of 3What this coversGHL Customer Care provides a comprehensive API platform that enables developers to build integrations, automations, and custom applications with the GHL Customer Care CRM and Marketplace. Our API includes REST endpoints for contacts, messaging, workflows, calendars, payments, webhooks, and more.
Fields in this part of the guideHigh-Level API DocumentationHow to Use Versioned API DocumentationHow to Get Help or Support for the GHL Customer Care APIHow to Submit a New API-Related Idea to GHL Customer CareDifferences Between API Access Across Plan LevelsFrequently Asked QuestionsHelp & Support
Buttons and menus referencedAll API DocumentationTABLE OF CONTENTS
Next stepPlease Note: Going forward, the ability to generate new API keys will be removed from both Agency and Sub-account settings.This change applies to accounts that have not yet generated or are not currently using a API key.All 8 steps in this procedure
High-Level API Documentation
How to Use Versioned API Documentation
How to Get Help or Support for the GHL Customer Care API
How to Submit a New API-Related Idea to GHL Customer Care
Differences Between API Access Across Plan Levels
What are the Rate Limits for API 1.0 & API 2.0?
Frequently Asked Questions
Help & Support
Please Note: Going forward, the ability to generate new API keys will be removed from both Agency and Sub-account settings.This change applies to accounts that have not yet generated or are not currently using a API key.
GHL Customer Care API documentation is now available at https://marketplace.https://ghlcustomercare.com/docs/. If you previously used the legacy Stoplight documentation, update your bookmarks. Stoplight documentation will be deprecated in the coming months.
GHL Customer Care API documentation now supports versioned API references. Developers can use the version switcher inside the API documentation to view endpoints, schemas, parameters, and examples for a specific API version. This helps teams maintain stable integrations, reference older API versions when needed, and plan upgrades to newer versions with more confidence.
Please Note: GHL Customer Care is also working toward the next API milestone, v3, which is expected to introduce enhanced capabilities, improved performance, and new endpoints for advanced use cases. Continue checking the official API documentation for the latest available versions.
How to Use Versioned API Documentation
Versioned API documentation helps developers build and maintain integrations against a specific API version. This reduces the risk of referencing the wrong endpoint structure, request schema, or response format when maintaining production systems or planning migrations.
Open the official GHL Customer Care API documentation.
Use the versionswitcher in the documentation to select the API version you want to reference.Step 2 of 5: Use the version switcher in the documentation to select the API…What this shows Step 2 of 5: Use the version switcher in the documentation to select the API version you want to reference.What this showsShows what to choose for step 2 of 5 in the "How to Use Versioned API Documentation" section of "GHL Customer Care API Documentation".This screenshot accompanies step 2 of 5 in the "How to Use Versioned API Documentation" section of "GHL Customer Care API Documentation". At this point in the walkthrough you use the version switcher in the documentation to select the API version you want to reference. The next step is to review the endpoints, request parameters, schemas, and response details for that selected version.Step 2 of 5Image 2 of 3What to chooseUse the version switcher in the documentation to select the API version you want to reference.
Buttons and menus referencedversionswitcherendpointsrequestparametersschemasresponsedetails
Next stepReview the endpoints, request parameters, schemas, and response details for that selected version.All 5 steps in this procedure
Open the official GHL Customer Care API documentation.
Use the version switcher in the documentation to select the API version you want to reference. this image
Review the endpoints, request parameters, schemas, and response details for that selected version.
Use older API versions when maintaining existing integrations.
Review newer versions when planning upgrades or building new integrations.
Review the endpoints, requestparameters, schemas, and responsedetails for that selected version.
Use older API versions when maintaining existing integrations.
Review newer versions when planning upgrades or building new integrations.
Versioned documentation does not impact existing integrations. It is designed to make API references clearer and more stable for developers.
Agency Sub-Account
Agency Sub-Account support allows eligible agencies to identify and manage the primary sub-account used for onboarding and configuration.
Document:
eligibility or plan scope
read/update endpoint behavior
audit implications if returned in API responses
any uniqueness rules, such as whether only one Agency Sub-Account can exist per agency
How to Get Help or Support for the GHL Customer Care API
IMPORTANT: At this time, GHL Customer Care Support does NOT provide setup code auditing or developer consultative services on API-Related topics. However, if your setup is complete and correct - yet an error persists, you may have encountered an API Bug we need to fix. You can report this bug by filling out this form: https://developers.https://ghlcustomercare.com/support
For any questions relating to the GHL Customer Care API, join the developer Slack group to ask our community of talented customers here: https://developers.https://ghlcustomercare.com/join-dev-community
GHL Customer Care Devs host a monthly Developer Council Call on the second to last Friday, which you can find on the events calendar here: https://ghlcustomercare.com/events
Check out our Developers Landing Page, where you can find the Developer Marketplace, Documentation, Slack Channel, and more! --> https://developers.https://ghlcustomercare.com/
Agent Studio also supports public APIs for managing agents programmatically. For Agent Studio-specific endpoints and usage guidance, refer to the dedicated Agent Studio API article.
How to Submit a New API-Related Idea to GHL Customer Care
Please Note: Our API Docs list all available endpoints that are publicly available. If you don’t see an endpoint on either of the API developer sites listed below, we recommend visiting our GitHub Issues page to submit your request.
Differences Between API Access Across Plan Levels
Basic API access is included with our Starter and Unlimited plans, while Advanced API access is available on our Agency Pro plan.
In addition to the future endpoints that will be released in our OAuth 2.0 API (which is only available in our Advanced API access), this tier unlocks the use of Agency API Keys, where lower plan levels only access Location API Keys.
Differences Between API Access Across Plan Levels (image 3 of 3)What this shows In addition to the future endpoints that will be released in our OAuth 2.0 API (which is only available in our Advanced API access), this…What this showsIllustrates the "Differences Between API Access Across Plan Levels" section of "GHL Customer Care API Documentation".This screenshot appears in the "Differences Between API Access Across Plan Levels" section of "GHL Customer Care API Documentation". The text alongside this image reads: In addition to the future endpoints that will be released in our OAuth 2.0 API (which is only available in our Advanced API access), this tier unlocks the use of Agency API Keys, where lower plan levels only access Location API Keys. Immediately after, the guide continues: GHL Customer Care has implemented rate limits on our public V2 APIs using OAuth to ensure optimal performance and stability. These limits have been adjusted to.Image 3 of 3What this coversIn addition to the future endpoints that will be released in our OAuth 2.0 API (which is only available in our Advanced API access), this tier unlocks the use of Agency API Keys, where lower plan levels only access Location API Keys.Next stepGHL Customer Care has implemented rate limits on our public V2 APIs using OAuth to ensure optimal performance and stability. These limits have been adjusted to:
What are the Rate Limits for API 1.0 & API 2.0?
GHL Customer Care has implemented rate limits on our public V2 APIs using OAuth to ensure optimal performance and stability. These limits have been adjusted to:
Burst limit: A maximum of 100 API requests per 10 seconds for each Marketplace app (i.e., client) per resource (i.e., Location or Company).
Daily limit: 200,000 API requests per day for each Marketplace app (i.e., client) per resource (i.e., Location or Company).
These new limits contribute to better overall performance and stability of our system.
To monitor your limited usage, refer to the following API response headers:
'X-RateLimit-Limit-Daily': Your daily limit
'X-RateLimit-Daily-Remaining': The remaining number of requests for the day
'X-RateLimit-Interval-Milliseconds': The time interval for burst requests
'X-RateLimit-Max': The maximum request limit in the specified time interval
'X-RateLimit-Remaining': The remaining number of requests in the current time interval.
Frequently Asked Questions
Q. What is the GHL Customer Care API used for?
The GHL Customer Care API allows developers to build custom integrations, automate workflows, and connect external applications with the GHL Customer Care platform. It provides REST endpoints for contacts, conversations, calendars, workflows, payments, and more.
Q. Does GHL Customer Care still support API V1?
No. GHL Customer Care API V1 has reached end-of-support. While existing integrations may continue to function, no updates or technical support are provided. Developers should migrate to API V2 for ongoing support and new features.
Q. What authentication methods does the GHL Customer Care API support?
GHL Customer Care supports:
Private Integration Tokens for internal or single-location integrations
OAuth 2.0 for public integrations and Marketplace apps requiring user authorization
Q. When should I use OAuth 2.0 instead of a Private Integration Token?
Use OAuth 2.0 when:
Building a public or Marketplace app
Accessing multiple locations or accounts
Requiring secure, user-approved access
Private Integration Tokens are best for internal tools or single-account use cases.
Q. What are the API rate limits in GHL Customer Care?
GHL Customer Care enforces:
100 requests per 10 seconds (per resource)
200,000 requests per day (per resource)
Rate limit headers are included in API responses to help track usage.
Q. Can GHL Customer Care Support help me build or debug my API integration?
No. GHL Customer Care Support does not provide hands-on API development or debugging assistance. For help, developers should:
Review the official API documentation
Join the GHL Customer Care Developer Community
Report bugs via the Developer Support portal
Q. Where can I find the official GHL Customer Care API documentation?
The official API documentation is available on the GHL Customer Care Developer Marketplace: https://marketplace.https://ghlcustomercare.com/docs/
Q. Is API access available on all GHL Customer Care plans?
API access varies by plan:
Starter & Unlimited: Basic API access
Agency Pro: Advanced API access, including OAuth and agency-level tokens
Some endpoints may only be available on higher plans.
Q. How do I request a new API feature or endpoint?
You can submit API feature requests or report documentation issues by creating an issue in the official GitHub repository for GHL Customer Care API docs.
Q. Does GHL Customer Care provide SDKs or webhooks?
Yes. GHL Customer Care offers webhooks for real-time event updates, and SDKs are available or supported for certain integrations. Refer to the API documentation for supported webhook events and SDK details.
Q. Can I view documentation for different API versions? Yes. GHL Customer Care API documentation now includes versioned references, allowing developers to select the API version they want to view from the version switcher.
Q. Does API documentation versioning affect my existing integrations? No. Versioned documentation does not impact existing integrations. It helps developers reference the correct API version and maintain stable integrations.
Q. Why should I select a specific API version in the documentation? Selecting a specific API version helps ensure you are reviewing the correct endpoints, schemas, request parameters, and response details for the version your integration uses.
Q. Are older API versions still documented? Yes. Older API versions remain accessible and documented so developers can maintain existing integrations and plan migrations more easily.
Q. Is API v3 available now? Not yet, based on the release note. GHL Customer Care is working on v3 as the next API milestone. Users should refer to the official API documentation for current availability.
Help & Support
GHL Customer Care Support does not provide hands-on API coding help or setup auditing. If you encounter issues:
1. For API Bugs
Report a bug directly here: https://developers.https://ghlcustomercare.com/support
2. Developer Community
Join the GHL Customer Care Dev Slack to collaborate with other developers: https://developers.https://ghlcustomercare.com/join-dev-community
Frequently asked questions
What are the Rate Limits for API 1.0 & API 2.0?
GHL Customer Care has implemented rate limits on our public V2 APIs using OAuth to ensure optimal performance and stability. These limits have been adjusted to: Burst limit : A maximum of 100 API requests per 10 seconds for each Marketplace app (i.e., client) per resource (i.e., Location or Company). Daily limit : 200,000 API requests per day for each Marketplace app (i.e., client) per resource (i.e., Location or Company). These new limits contribute to better overall performance and stability of our system. To monitor your limited usage, refer to the following API response headers: 'X-RateLimit-Limit-Daily': Your daily limit 'X-RateLimit-Daily-Remaining': The remaining number of requests for the day 'X-RateLimit-Interval-Milliseconds' : The time interval for burst requests 'X-RateLimit-Max': The maximum request limit in the specified time interval 'X-RateLimit-Remaining': The remaining number of…
