Access to the Custom Fields API requires your GHL API credentials. Use OAuth tokens or an API key as configured in your GHL account, and include the token in request headers.
0CodeKit uses your GHL credentials to authorize requests. Store tokens securely and rotate them as needed when connecting to endpoints.
– 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
Trigger: When a location is selected, fetch its customValues and update specific entries as needed.
Actions: Use GET /locations/:locationId/customValues and PUT /locations/:locationId/customValues/:id to modify values.
GET /locations/:locationId/customValues, PUT /locations/:locationId/customValues/:id
Key fields: locationId, id, value, and field key.
Trigger: When updating multiple values, use POST to create and PUT to update.
Actions: POST /locations/:locationId/customValues, PUT /locations/:locationId/customValues/:id, optional DELETE when needed.
POST /locations/:locationId/customValues
Key fields: locationId, value set, and id.
Trigger: When you need structure, fetch customFields definitions.
Actions: GET endpoints related to customFields: 7-9 and 12-15.
GET /locations/:locationId/customFields, GET /locations/:locationId/customFields/:id, GET /custom-fields/:id
Key fields: locationId, id, fieldKey.
Benefit: Faster access to location-specific data and cleaner automation.
Benefit: Centralized control of field definitions and values across locations.
Benefit: Smooth Zapier automation via a robust REST API surface.
This section defines core elements (endpoints, methods, IDs, values, fields) and the processes to authenticate, request, update, and review data across the Custom Fields API.
The GHL API provides programmatic access to endpoints for managing locations, custom values, and custom fields.
An individual URL that performs a specific action on a resource.
A location in GHL where data such as custom values and fields are stored.
A single data item assigned to a field for a given location.
Create a profile per location with its custom values to power personalized automations.
Use webhook-driven updates to keep fields in sync across apps.
Format data for sharing with stakeholders in clean, consistent exports.
Collect your GHL API key or OAuth token and note your location IDs for targets.
Run sample requests to verify access to customValues and customFields endpoints.
Configure 0CodeKit workflows to read, write, and update values across automation flows.
Endpoint coverage includes GET /locations/:locationId/customValues for retrieval, GET /locations/:locationId/customValues/:id for specific values, and POST /locations/:locationId/customValues to create values.\n\nAdditionally, PUT and DELETE variants allow updates and removals by value ID. Use the endpoints in the list to build your flows.
Authentication uses your GHL API credentials. Use OAuth tokens or API keys as configured in your GHL account, and send the token in your request headers.\n\nRefresh tokens and secure storage are recommended; avoid embedding secrets in client-side code.
Yes. Use POST to create multiple values and PUT to update specific ones. The endpoints support batch-like operations when you loop through data in your automation.\n\nBe mindful of rate limits and validate responses per item during batch processing.
Custom Fields endpoints like GET /locations/:locationId/customFields and GET /custom-fields/:id expose field definitions and metadata.\nTags are available via GET /locations/:locationId/tags for organization and filtering.
A custom value is the actual data assigned to a field for a given location, such as a text string, number, or date.\nFields define what data can be stored for each location, while values hold the content.
Exporting data can be done by reading endpoints and sending the retrieved data to your reporting tool or spreadsheet.\nFormat results consistently (field names, types, and values) for reliable downstream use.
Location IDs are available in your GHL account or through API responses that include locationId.\nField definitions are exposed via customFields endpoints and in /custom-fields/:id responses.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
