Authenticate requests with your GHL credentials. Include an API key or Bearer token in the Authorization header when calling endpoints.
Securely connect Acadimiat to the GHL using API keys and OAuth tokens issued to your app. Rotate credentials regularly and restrict scopes to payments, orders, and subscriptions.
Key endpoints involved: – GET /payments/integrations/provider/whitelabel – payments/integration.write – POST /payments/integrations/provider/whitelabel – payments/orders.readonly – GET /payments/orders/ – GET /payments/orders/:orderId – GET /payments/orders/:orderId/fulfillments – payments/orders.write – POST /payments/orders/:orderId/fulfillments – payments/transactions.readonly – GET /payments/transactions/ – GET /payments/transactions/:transactionId – payments/subscriptions.readonly – GET /payments/subscriptions/ – GET /payments/subscriptions/:subscriptionId
Trigger: when a new order is created in Acadimiat, create the corresponding order in the Orders API and initiate fulfillment.
Actions: create the order, create the initial fulfillment, and sync status between both systems.
POST /payments/orders/:orderId/fulfillments
orderId, fulfillmentId, totalAmount, currency, status
Trigger: when a payment completes in Acadimiat, record a transaction in the Orders API.
Actions: log the transaction, update the related order, and timestamp the event.
GET /payments/transactions/
transactionId, orderId, amount, currency, status, timestamp
Trigger: when a subscription is updated in Acadimiat, reflect changes in the Orders API.
Actions: create or update subscriptions and schedule next billing date.
GET /payments/subscriptions/
subscriptionId, planId, nextBillingDate, status, amount
No-code setup with ready-made endpoints and triggers.
Real-time visibility into sync status and health.
Scalable integration that grows with your business.
Key elements include endpoints, triggers, actions, data mappings, and error handling. Common data fields include orderId, fulfillmentId, transactionId, subscriptionId, amount, currency, and status.
Application Programming Interface: a set of rules that lets apps talk to each other, e.g., Acadimiat talking to the Orders API.
A specific URL path and method to perform an action in an API.
Process of proving identity to access API resources.
The process of completing an order or service delivery.
Use automated triggers to create orders and automatically fulfill them, reducing manual steps.
Build a dashboard to reconcile orders, payments, and fulfillments in real-time.
Automate subscription billing updates between Acadimiat and Orders API.
Collect API keys for GHL and Acadimiat, then set permissions for orders, transactions, and subscriptions.
Map each trigger to the corresponding endpoint in the Orders API and enable webhooks where available.
Run test scenarios to verify data flow, error handling, and retries.
The Orders API exposes endpoints to read and manage payments, orders, fulfillments, transactions, and subscriptions. Depending on your plan, you can access readonly endpoints for safe data retrieval. You can combine with Acadimiat to automate workflows without code using Zapier or direct API calls.
No-code options are available via automation platforms that connect Acadimiat to the Orders API. You can configure triggers, actions, and webhooks without writing code. If custom logic is required, you can extend workflows with code blocks in your Zapier app or your integration layer.
Security is enforced through API keys, scoped access, OAuth tokens, and HTTPS. Always use the least-privilege scopes necessary for your integration. Rotate credentials regularly and monitor access logs for unusual activity.
Yes. You can retrieve historical transactions by querying GET /payments/transactions/ and applying date ranges if available. Combine with order history to reconcile past payments and fulfillments.
If a sync fails, automatic retries are attempted and error details are captured in logs. Review the error codes, adjust retry settings, and re-run the failed scenario. Ensure endpoints are reachable and credentials are valid.
Webhooks are supported for real-time updates on orders, transactions, and fulfillments. Configure delivery URLs and verify signatures. Use retries and idempotent operations to handle duplicate events gracefully.
Common authentication issues include expired tokens or revoked keys. Regenerate credentials, re-authenticate in both apps, and verify environment (sandbox vs. production). Ensure the correct scopes are granted for payments, orders, and subscriptions.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
