Secure access is required to fetch and update custom values. Use OAuth 2.0 tokens or API keys supported by your GHL plan.
Assign appropriate permissions to prevent unauthorized access and ensure data integrity for Accredible Certificates.
– GET /locations/:locationId/customValues: Retrieve all custom values for a location.\n- GET /locations/:locationId/customValues/:id: Retrieve a specific custom value.\n- POST /locations/:locationId/customValues: Create a new custom value.\n- PUT /locations/:locationId/customValues/:id: Update an existing custom value.\n- DELETE /locations/:locationId/customValues/:id: Remove a custom value.\n- GET /locations/:locationId/customFields: List custom fields for a location.\n- GET /locations/:locationId/customFields/:id: Get a specific custom field.\n- GET /custom-fields/:id: Retrieve a custom field by ID.\n- GET /custom-field/object-key/:key: Find a field by its object key.\n- POST /locations/:locationId/customFields: Create a new custom field.\n- PUT /locations/:locationId/customFields/:id: Update a custom field.\n- DELETE /locations/:locationId/customFields/:id: Delete a custom field.
Trigger: when a value is updated in GHL, pull the change and push to Accredible.
Actions: GET /locations/:locationId/customValues, then upsert to Accredible’s corresponding field.
METHOD: GET /locations/:locationId/customValues
Key fields: id, locationId, value, updatedAt
Trigger: new or changed field definitions in GHL.
Actions: POST /locations/:locationId/customValues to add or PUT /locations/:locationId/customValues/:id to update.
METHOD PATHS: POST /locations/:locationId/customValues and PUT /locations/:locationId/customValues/:id
Key fields: id, locationId, value, name
Trigger: deprecated fields are marked and removed.
Actions: DELETE /locations/:locationId/customValues/:id
METHOD PATH: DELETE /locations/:locationId/customValues/:id
Key fields: id, locationId
Benefit 1: Visual workflows without coding.
Benefit 2: Real-time data synchronization between GHL and Accredible.
Benefit 3: Centralized control over custom fields.
This glossary covers endpoints, authentication, terminology, and data mapping used in the integration.
A unique URL that allows a specific operation on data in the GHL API.
The process of proving identity to access the API, typically via OAuth tokens or API keys.
A method for receiving real-time notifications when data changes.
A standard for secure, token-based authorization used by modern APIs.
Automatically pull updated values from GHL and populate corresponding Accredible certificate fields.
Create or update Accredible certificates when a relevant GHL event occurs.
Validate field values before they are saved to Accredible to ensure data quality.
Collect your locationId, field IDs, and the Accredible certificate field mappings.
Configure OAuth keys or API keys and test access.
Map endpoints to Accredible fields, perform test runs, then enable automation.
The scope for Custom Fields API is defined by your GHL plan. For read-only access to custom values use locations/customValues.readonly. This lets you pull existing values into Accredible Certificates for display and reporting. If you need to write values, enable locations/customValues.write through your admin settings.\n\nAlways apply the principle of least privilege, granting only the permissions needed and rotating credentials regularly to keep data secure.
You can use the endpoints without writing a custom backend if your automation platform supports REST calls. Many users leverage workflows to call endpoints and map fields.\n\nFor complex mappings or transformations, a lightweight script or middleware can help ensure data formats align between GHL and Accredible.
Yes. You can delete a custom value with DELETE /locations/:locationId/customValues/:id, provided you have the necessary permissions.\n\nIf you need to preserve history, consider archiving instead or marking values as inactive before deletion.
Authentication is typically done via OAuth 2.0 tokens or API keys. Store credentials securely and rotate them regularly.\nIn GHL, configure your app credentials and test access against the endpoints listed to verify permissions.
Endpoints used for managing custom fields include GET /locations/:locationId/customFields, GET /custom-fields/:id, POST /locations/:locationId/customFields, PUT /locations/:locationId/customFields/:id, and DELETE /locations/:locationId/customFields/:id.\nFor values, use GET /locations/:locationId/customValues, GET /locations/:locationId/customValues/:id, POST /locations/:locationId/customValues, PUT /locations/:locationId/customValues/:id, and DELETE /locations/:locationId/customValues/:id.
A field describes the metadata (name, type, allowed values) for a piece of data. A value is the actual content for that field on a given record.\nFields are defined once per location; values vary per record and can be updated via the API.
Yes. You can set up triggers in GHL to call endpoints or have your automation fetch changes and update Accredible certificates accordingly.\nTest the end-to-end flow to ensure updates propagate correctly and monitor for any mapping errors.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
