Authenticate requests with the provided GHL credentials using the scope payments/integration.readonly. Store credentials securely, rotate keys regularly, and follow least-privilege access for best security.
Authorize AccessAlly actions via API keys or OAuth, with scopes limited to payments, orders, and memberships. Keep credentials private and rotate them after changes.
Core endpoints include: GET /payments/integrations/provider/whitelabel; POST /payments/integrations/provider/whitelabel; GET /payments/orders/; GET /payments/orders/:orderId; GET /payments/orders/:orderId/fulfillments; POST /payments/orders/:orderId/fulfillments; GET /payments/transactions/; GET /payments/transactions/:transactionId; GET /payments/subscriptions/; GET /payments/subscriptions/:subscriptionId. There is a separate permissions token payments/integration.write for write access.
Triggered when provider whitelabel data changes to keep provider configuration in sync with AccessAlly.
Actions: fetch and update provider whitelabel records; create new whitelabel mappings as needed.
Paths: GET /payments/integrations/provider/whitelabel; POST /payments/integrations/provider/whitelabel
Key fields: providerId, whitelabelName, status
Triggered on order lifecycle events to synchronize order data with AccessAlly.
Actions: read orders, read fulfillments, create fulfillments when needed.
Paths: GET /payments/orders/; GET /payments/orders/:orderId; GET /payments/orders/:orderId/fulfillments; POST /payments/orders/:orderId/fulfillments
Key fields: orderId, fulfillmentId, status
Triggered on new transactions or subscription updates to reflect payment status in AccessAlly.
Actions: read transactions, read subscriptions, monitor for changes.
Paths: GET /payments/transactions/; GET /payments/transactions/:transactionId; GET /payments/subscriptions/; GET /payments/subscriptions/:subscriptionId
Key fields: transactionId, subscriptionId, status
Fast integration without custom code, using ready-made endpoints and mappings.
Secure, auditable data flow between payments and memberships.
Scalable solution that grows with your memberships and orders.
Elements include API endpoints, authentication, data mapping between GHL and AccessAlly, webhooks, and fulfillment workflows.
A specific URL path you call to perform an action in the API.
Proof of identity that grants access to resources and endpoints.
A callback URL that notifies your app about events as they occur.
The completion of an order, including delivery or access activation.
When a payment is confirmed, automatically enroll the customer in AccessAlly to unlock memberships.
Keep AccessAlly membership statuses in sync with payment events to avoid manual updates.
Propagate refunds from orders to AccessAlly to adjust or revoke access immediately.
Collect your GHL API credentials with the correct scope and obtain AccessAlly API keys.
Enable the required endpoints in GHL and map fields to AccessAlly data structures.
Run end-to-end tests, validate data synchronization, and move to production with monitoring.
No extensive coding is required thanks to the no-code-friendly endpoints and mappings. Use the built-in connectors to link GHL and AccessAlly, and script only if you need highly customized workflows. For most teams, basic setup is enough to start syncing orders and payments.
Data shared includes payment status, order details, fulfillment status, and subscription activity. AccessAlly can reflect current access based on payments, while GHL can trigger actions when payments or orders change.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
