LeadConnector

Overview

Property	Value
Slug	`gohighlevel`
Auth	OAuth 2.0
API version	v1
Sandbox	No
Rate limit	60 req/min, 5 req/sec

Supported resources

Resource	List	Get	Create	Update	Delete
Contact	✓	✓	✓	✓	✓
Lead	✓	✓	✓	✓	✓
Deal	✓	✓	✓	✓	✓
Meeting	—	—	—	—	—
Company	—	—	—	—	—
Note	✓	✓	✓	✓	✓
Task	✓	✓	✓	✓	✓
Activity	—	—	—	—	—
Pipeline	✓	✓	—	—	—
Owner	✓	✓	—	—	—
Appointment	✓	✓	✓	✓	✓

In LeadConnector, leads and deals both map to Opportunities. LeadConnector has no distinct “meeting” entity — calendar events ARE appointments — so RouteMCP exposes only appointment for LeadConnector. Use the appointment resource for any calendar event work.

Connect setup

LeadConnector uses OAuth 2.0 (without PKCE). You need a Marketplace App from the LeadConnector developer portal.

Create a LeadConnector marketplace app

Go to the Developer Marketplace → Developer → Apps → Create App. Copy the Client ID and Client Secret.

Add the redirect URL

In your app’s Redirect URL field, add:

https://api.routemcp.io/api/v1/auth/callback

Configure required scopes

Enable the following scopes:

contacts.readonly
contacts.write
opportunities.readonly
opportunities.write
calendars/events.readonly
calendars/events.write
calendars.readonly
calendars.write
users.readonly

Connect via the widget

When your end user opens the Connect widget, they enter the Client ID and Client Secret, then authorize via the LeadConnector OAuth flow which prompts them to select a location (sub-account).

Usage

# List contacts from LeadConnector
curl "https://api.routemcp.io/api/v1/crm/contact?provider=gohighlevel" \
  -H "Authorization: Bearer sk_live_your_key" \
  -H "X-End-User-Id: user-123"

# Create a contact
curl -X POST "https://api.routemcp.io/api/v1/crm/contact?provider=gohighlevel" \
  -H "Authorization: Bearer sk_live_your_key" \
  -H "Content-Type: application/json" \
  -H "X-End-User-Id: user-123" \
  -d '{ "first_name": "Jane", "last_name": "Doe", "email_addresses": [{ "email_address": "jane@example.com", "email_address_type": "Work" }] }'

Notes

LeadConnector does not offer a sandbox environment. Test with a dedicated test location in your account.
The OAuth flow requires the end user to select a location (sub-account) during authorization.
Contacts support additional fields: tags, doNotContact (DND flag), lead_source, and dateOfBirth.

Overview

CRM

Accounting

Calendar

Developer

Productivity

Documents & Storage

Communication

Project Management

Database

Overview

Supported resources

Connect setup

Usage

Notes

​Overview

​Supported resources

​Connect setup

​Usage

​Notes

Overview

Supported resources

Connect setup

Usage

Notes