Authenticate to the Custom Fields API using your GHL credentials. Scope is locations/customValues.readonly to protect data while enabling read access for integration flows.
For 97Display use the same access token or API key authorized for the GHL account. Treat credentials as sensitive and rotate them regularly.
GET /locations/:locationId/customValues; GET /locations/:locationId/customValues/:id; POST /locations/:locationId/customValues; PUT /locations/:locationId/customValues/:id; GET /locations/:locationId/customFields; GET /locations/:locationId/customFields/:id; GET /locations/:locationId/tags; GET /locations/:locationId/customFields; GET /custom-fields/:id; GET /custom-field/object-key/:key; POST /locations/:locationId/customFields; PUT /locations/:locationId/customFields/:id; DELETE /locations/:locationId/customFields/:id; GET /custom-fields/:id; GET /locations/:locationId/tags
Trigger: A location is selected in 97Display, fetch its custom values from GHL.
Actions: GET /locations/:locationId/customValues to retrieve; GET /locations/:locationId/customValues/:id to fetch a specific value.
Method Path: GET
Key fields: locationId, id, value
Trigger: Add or modify a custom value from 97Display.
Actions: POST /locations/:locationId/customValues to create; PUT /locations/:locationId/customValues/:id to update.
Method Path: POST, PUT
Key fields: locationId, payload with custom value data
Trigger: Update field definitions as your schema evolves.
Method Path: GET, POST, PUT, DELETE
Key fields: locationId, id, fieldId
No-code setup lets marketers connect data without writing code.
Visual workflows in Zapier or automation tools to sync fields across apps.
Fast, scalable access to location data and custom values.
A concise glossary of terms and processes used in integrating the GHL Custom Fields API with 97Display.
Application Programming Interface a set of rules that allows apps to read and modify data like custom values and fields in GHL.
OAuth 2.0 is the standard protocol for securely authorizing access to GHL APIs.
RESTful endpoints such as /locations/:locationId/… used to perform actions on resources like custom values and fields.
Webhook events enable real time updates between GHL and connected apps.
Set up a trigger in your automation tool to push new locations custom values from GHL into 97Display as soon as they appear.
Use endpoint data to automatically adjust field mappings in 97Display when customFields definitions change.
Create dashboards showing field completeness, consistency, and freshness across locations.
Obtain an API key or OAuth token for the Custom Fields API and authorize 97Display.
Connect endpoints such as /locations/:locationId/customValues and /locations/:locationId/customFields to your automated flows in 97Display.
Run tests to map fields confirm data freshness and set up monitoring alerts.
Authentication to the Custom Fields API is typically done with an API key or OAuth token issued by your GHL account. Keep credentials secure and scoped to your required permissions locations/customValues.readonly.
Basic retrieval uses GET endpoints like GET /locations/:locationId/customValues and GET /custom-fields/:id. For updates use PUT or POST endpoints as appropriate to the resource. Ensure locationId is supplied and that the scope includes the necessary permissions.
Yes you can create and update custom values and fields using POST and PUT endpoints. Provide required payload fields and IDs. Validate responses and handle 4xx/5xx errors gracefully.
Store credentials securely use environment variables restrict access and implement token rotation. Use least privilege scopes and monitor logs for anomalies.
Handle errors with standard HTTP status codes; implement retries with exponential backoff. Respect 429 limits and back off accordingly; set timeouts and provide fallback values.
Yes you can automate no code workflows using tools like Zapier to connect GHL Custom Fields API with 97Display without writing code.
Docs and endpoint references are available in your GHL developer portal and the integration guide for 97Display. Use sample payloads to test in a sandbox.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
