Authenticate requests with your GHL API credentials and ensure the scope locations/customValues.readonly is granted. Use a secure API key and rotate credentials regularly.
Authorizing the Accelevents connector requires your API credentials from both sides. Store keys securely and grant the connector access to location data and custom values.
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; POST /locations/:locationId/customFields; PUT /locations/:locationId/customFields/:id; GET /custom-fields/:id; GET /custom-field/object-key/:key; GET /locations/:locationId/tags
Trigger when a location is updated in GHL to pull the latest custom values into Accelevents.
Actions: call GET /locations/:locationId/customValues and update corresponding fields in Accelevents.
GET /locations/:locationId/customValues
locationId, id, value
Trigger when a field changes; push updates via PUT to keep Accelevents in sync.
Actions: use PUT /locations/:locationId/customFields/:id to sync changes.
PUT /locations/:locationId/customFields/:id
locationId, id, fieldKey, value
Trigger when new data is required for a event or attendee type; create via POST.
Actions: post new values to /locations/:locationId/customValues and map them to Accelevents fields.
POST /locations/:locationId/customValues
locationId, newValueData
Automate the synchronization of location-specific data to power reports and attendee experiences without writing code.
Reduce manual data entry and human error by leveraging automated field mappings and endpoints.
Speed onboarding for new venues and events with ready-to-use field mappings and endpoints.
This glossary explains API terms, data elements, and processes you’ll encounter when integrating the Custom Fields API with Accelevents.
Application Programming Interface: a set of rules that lets two software systems talk to each other.
The process of granting access to use an API and its data, typically via tokens or keys.
A specific URL in an API that performs a defined action, such as retrieving or updating data.
A callback mechanism where a service notifies your app when an event occurs.
Capture attendee preferences in GHL and surface them in Accelevents for tailored agendas.
Use custom values to suggest sessions based on attendee data.
Show up-to-date venue or room availability by syncing custom values.
Grab your GHL API key and Accelevents access tokens, and confirm the proper scopes are granted.
Decide which GHL custom fields map to Accelevents fields and set up sync rules.
Run test migrations, verify data integrity, and enable live syncing.
The Custom Fields API exposes location-based custom values and fields that you can read and manage programmatically. It enables automation and integrations without manual data entry. You can pull, create, update, and delete values and fields as needed to keep your event data aligned across systems.
Key endpoints include GET /locations/:locationId/customValues, GET /locations/:locationId/customFields, and POST/PUT for creating or updating values and fields. You can also fetch specific items by ID and review the object-key mapping for seamless data transfer.
Authentication uses API keys or OAuth with the required scope, such as locations/customValues.readonly. Keep credentials secure, rotate them regularly, and apply least-privilege access.
No-code options are available via Zapier App Connector and other integrations, letting you map fields and set up workflows without writing code. Advanced users can leverage endpoints directly for greater control.
To test, run a sandbox or staging synchronization, review the results in Accelevents, and monitor logs for any errors. Validate that locationId and field mappings are correct before going live.
You can sync location custom values and custom fields, including identifiers, names, keys, and corresponding values. Data types and field definitions depend on how you configure mappings in GHL and Accelevents.
If you encounter issues, verify endpoint permissions, confirm locationId and field keys, review authentication tokens, and consult the API documentation for any endpoint-specific requirements.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
