Access is secured via API keys or OAuth per GHL guidelines. Store tokens securely and scope access to needed resources.
Authenticate 17hats with your API credentials and grant the necessary permissions to read and write custom data.
GET /locations/:locationId/customValues; GET /locations/:locationId/customValues/:id; locations/customValues.write; POST /locations/:locationId/customValues; PUT /locations/:locationId/customValues/:id; DELETE /locations/:locationId/customValues/:id; locations/customFields.readonly; GET /locations/:locationId/customFields; GET /locations/:locationId/customFields/:id; GET /custom-fields/:id; GET /custom-field/object-key/:key; locations/customFields.write; POST /locations/:locationId/customFields; PUT /locations/:locationId/customFields/:id; DELETE /locations/:locationId/customFields/:id; locations/tags.readonly; GET /locations/:locationId/tags
When a location’s custom values are read or updated in 17hats, pull the latest data into GHL to keep records in sync.
Actions: call GET /locations/:locationId/customValues to fetch, map fields to GHL values, and push to GHL where needed.
GET /locations/:locationId/customValues
Fields: locationId, id, value, name
Trigger when new values are created in 17hats, then POST or PUT to the corresponding endpoint in GHL.
POST /locations/:locationId/customValues; PUT /locations/:locationId/customValues/:id
Fields: locationId, id, value, name
Trigger when custom fields definitions change in 17hats; reflect changes in GHL via GET/PUT on /customFields and related endpoints.
Actions: GET /locations/:locationId/customFields, GET /custom-fields/:id, PUT /locations/:locationId/customFields/:id to update; GET /locations/:locationId/tags to organize segmenting.
GET /locations/:locationId/customFields; GET /custom-fields/:id; PUT /locations/:locationId/customFields/:id; GET /locations/:locationId/tags
Fields: locationId, id, fieldKey
Automated data syncing eliminates manual updates and reduces errors.
Unified customer profiles across apps enable better segmentation and personalization.
Flexible automation using triggers and mappings speeds up onboarding and workflows.
Key elements: API endpoints, authentication, data mapping, endpoints for custom values and fields, and related resources like tags.
Application Programming Interface that lets applications talk to each other to read or update data in real time.
A mechanism that sends real-time data updates from one app to another when a trigger occurs, often used with integrations.
Methods to verify identity and authorize access to APIs, typically API keys or OAuth tokens.
A named data point within an object — in this page, a custom field value or metadata element.
Automatically mirror key contact fields from 17hats into GHL so sales and marketing have consistent data.
Populate GHL custom fields based on 17hats form submissions to tailor follow-ups.
Track updates between apps to build an audit trail for compliance and analysis.
Get your API keys or OAuth tokens and grant access to the required scopes for custom values and fields.
Define how 17hats fields map to GHL fields to ensure consistent data transfer.
Run test transfers, verify data integrity, and deploy automated workflows.
The GHL Custom Fields API lets systems read and write custom values and fields. It enables you to pull location-specific data into GHL and push updates back to your source apps. This creates a unified data layer across tools.
Basic connections can be achieved with no-code or low-code tools using API keys or OAuth. Some familiarity with JSON and endpoints helps, but you can start with guided templates.
Essential endpoints include reading and writing custom values and fields, plus retrieving field metadata and tags. The exact set you use depends on your workflow.
Security is important: rotate keys, use scoped permissions, and employ secure storage and encrypted transmission. Follow security best practices and audit logs to detect anomalies.
Yes. You can map several fields at once by batching requests or using bulk endpoints when supported by the API. Plan migrations during low-traffic windows to minimize impact.
Audit logs and dashboard views in GHL and your source app help you track sync events, successes, and errors. Use these insights to troubleshoot and improve data quality.
Yes. You can trigger automations in GHL based on changes detected via the API, enabling proactive workflows. Configure webhooks or polling to respond to updates in near real time.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
