Use OAuth 2.0 to securely access the Opportunities API. The requested scope is opportunities.readonly by default; request additional scopes as needed and store tokens securely in Acadimiat.
Configure your Acadimiat app with client_id and client_secret, enable token refresh, and rotate credentials regularly to keep connections secure.
GET /opportunities/search — search opportunities; GET /opportunities/:id — read a specific opportunity; GET /opportunities/pipelines — list pipelines; POST /opportunities — create an opportunity; PUT /opportunities/:id — update an opportunity; PUT /opportunities/:id/status — update the status; DELETE /opportunities/:id — delete an opportunity
Trigger: A new opportunity is created in Acadimiat, then a matching record is created in the Opportunities API.
Actions: POST /opportunities to create; GET /opportunities/:id to verify; PUT /opportunities/:id to update status when needed.
POST /opportunities
Key fields: name, pipeline_id, stage, amount, close_date
Trigger: Status changes in Opportunities API are pushed back to Acadimiat.
Actions: GET /opportunities/:id to pull details; PUT /opportunities/:id/status to push updates; optionally subscribe to webhooks.
PUT /opportunities/:id/status
Key fields: id, status, update_timestamp
Trigger: Periodic pull of pipeline data to monitor health and performance.
Actions: GET /opportunities/pipelines to fetch pipeline data; generate dashboards in Acadimiat.
GET /opportunities/pipelines
Key fields: pipeline_id, name, stage_counts, win_rate
Automate data flow with drag-and-drop automations in Acadimiat—no coding required.
Turn opportunities into automated actions and tasks without writing code.
Real-time syncing reduces manual updates and human error.
This glossary defines essential terms and processes used to connect Acadimiat with the Opportunities API, including endpoints, authentication, and data mapping.
A specific URL path that performs a defined operation (for example, GET /opportunities/search).
The method of proving identity and permissions to access the API, typically via OAuth 2.0 tokens.
A live URL in Acadimiat that receives real-time notifications when data changes in the Opportunities API.
The maximum number of API calls allowed in a given window to prevent abuse.
Capture new leads in Acadimiat forms and automatically create opportunities in the Opportunities API using POST /opportunities, then assign owners and stages.
Pull pipeline data with GET /opportunities/pipelines and display status, totals, and win rates in a real-time dashboard in Acadimiat.
Sync status changes from Opportunities API to Acadimiat and back, ensuring both systems reflect the latest stage.
Obtain OAuth tokens for the Opportunities API and configure Acadimiat to store credentials securely.
Map fields between Acadimiat and Opportunities API (name, pipeline_id, stage, amount, close_date).
Set up triggers and run tests to verify data flows before going live.
No coding is required for most common scenarios thanks to Acadimiat’s no-code builder. You can configure triggers, actions, and field mappings with a visual interface. For advanced needs, you can add lightweight scripts within Acadimiat to tailor behavior.
Essential endpoints for a basic sync include GET /opportunities/search to fetch opportunities, GET /opportunities/:id to read details, POST /opportunities to create, and PUT /opportunities/:id/status to update. Start with these and expand as needed.
The integration uses OAuth 2.0 tokens and TLS encryption for data in transit. Tokens are rotated and stored securely; audit logs track access and changes.
Yes. You can map key fields such as name, amount, pipeline, stage, and close_date. Acadimiat provides a field mapper to align data between the Opportunities API and your Acadimiat records.
Use the built-in test mode to simulate triggers and verify the data flow. You can also run a sandbox to see how new or updated opportunities propagate across systems before going live.
If an endpoint changes, update the connector configuration and re-test. Subscribe to API release notes and consider versioned endpoints to minimize disruption.
API usage and limits are shown in your GHL account dashboard. The Opportunities API scope provides the intended access; monitor rate limits during heavy synchronization to stay under quotas.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
