Authenticate to the Custom Objects API using secure tokens and OAuth scopes to protect your data and ensure reliable calls.
Configure Acadimiat to store and rotate credentials safely, then authorize requests to GHL’s API.
1) GET /objects/:key — retrieve a single object by key; 2) GET /objects — list all objects; 3) objects/schema.write — update object schemas; 4) objects/record.readonly — read records; 5) GET /objects/:schemaKey/records/:id — fetch a specific record; 6) objects/record.write — create or modify records; 7) POST /objects/:schemaKey/records — create a new record; 8) PUT /objects/:schemaKey/records/:id — update a record; 9) DELETE /objects/:schemaKey/records/:id — delete a record; 10-17: endpoints available on request/in development.
Trigger: changes in Acadimiat or GHL initiate synced actions between systems.
Actions: create, read, update, and delete object records using the defined endpoints.
Example methods: GET /objects/:key, POST /objects/:schemaKey/records, PUT /objects/:schemaKey/records/:id.
Key fields: key, schemaKey, id, and object field mappings.
Trigger: new or updated Acadimiat objects kick off a Zapier workflow to update GHL.
Actions: create or update GHL records from Zapier, pull data into Acadimiat, and trigger downstream steps.
Use Webhooks by Zapier to call the endpoints listed above and map fields.
Key fields: webhook URL, authentication, schemaKey, and record IDs.
Trigger: enrich Acadimiat records with GHL data for richer reports.
Actions: augment fields, calculate derived values, and export to dashboards or BI tools.
Leverage schema and object endpoints to fetch and enrich data on demand.
Key fields: schemaKey, object keys, and enrichment field mappings.
Automate data flow between Acadimiat and GHL without writing code, using Zapier and webhooks.
Centralize object management and authorization in a single no-code workflow.
Speed up deployments with reusable templates and starter workflows.
Key concepts: API, endpoints, schema, records, fields, authentication, and webhooks. This guide explains each term in the Acadimiat ↔ Custom Objects API integration.
Application Programming Interface: a set of rules that lets apps talk to each other and exchange data.
Defines objects, their fields, relationships, and validation for the Custom Objects API.
A specific URL path that performs an action on the API.
A single row of data within an object, identified by an ID.
Set up live synchronization to keep objects in sync across platforms.
Create conditional paths that react to object field values and automate actions.
Enrich Acadimiat data with GHL information for richer dashboards and insights.
Obtain API key, OAuth credentials, and client details from GHL and securely store them in Acadimiat.
In Acadimiat, connect to the endpoints listed above and map fields between objects.
Run tests, verify responses, and deploy with monitoring and alerts enabled.
No code required for the basics. Use the pre-built connectors in Acadimiat and Zapier to map fields and automate flows. For advanced scenarios, refer to the REST endpoints to customize your object operations. Regularly review your API usage to stay within limits.
Most common needs can be achieved with no-code configurations. If you require custom logic, you can add conditional steps within Zapier or use webhooks to trigger external processes. Complex validations may still need lightweight scripting, but the core integrations remain code-free.
GHL supports secure authentication (OAuth2, tokens) over encrypted connections. Use scoped tokens and rotate credentials regularly. Always store credentials in a secure vault and restrict access by role.
Start with GET /objects/:key and GET /objects to understand the data model. Then try creating a record with POST /objects/:schemaKey/records. These endpoints cover common tasks without writing custom code.
Yes. You can customize schemas and fields in GHL’s Custom Objects API and map them to Acadimiat fields in your Zapier workflows. Ensure field types and max lengths are consistent across systems.
In Zapier, create a Zap that uses Webhooks to call the GHL endpoints and test the results. Check response codes, payloads, and error handling. Use test data to verify end-to-end flows.
Rate limits vary by plan. Refer to GHL documentation for current quotas and best practices such as batching requests, reuse of connections, and exponential backoff.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
