Authenticate requests between GHL and Orders API with API keys, OAuth tokens, or secure credentials. Store credentials securely and rotate them regularly.
Authenticate with 46elks using API keys or tokens from your 46elks account. Keep credentials confidential and apply least-privilege access.
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; payments/orders.readonly; payments/orders.write; payments/transactions.readonly; payments/subscriptions.readonly
Trigger on new order creation in Orders API to automatically create a fulfillment in 46elks and notify the customer.
Actions: pull order details, post fulfillments, update order status, and send customer notifications.
Use GET /payments/orders/ to fetch orders and POST /payments/orders/:orderId/fulfillments to create fulfillments.
orderId, fulfillmentId, status, trackingNumber, totalAmount
Trigger on new transaction or update to keep payment data aligned between systems.
Actions: read from GET /payments/transactions/ and GET /payments/subscriptions/ as needed, update related records.
Endpoints: GET /payments/transactions/, GET /payments/subscriptions/
transactionId, subscriptionId, amount, currency, status
Trigger on subscription events to manage renewals and billing in real time.
Actions: GET /payments/subscriptions/, GET /payments/subscriptions/:subscriptionId
Endpoints: GET /payments/subscriptions/, GET /payments/subscriptions/:subscriptionId
subscriptionId, status, planId, nextBillingDate
No‑code automation lets you automate order confirmations, status changes, and customer notifications.
Build workflows with drag‑and‑drop logic to trigger SMS alerts and fulfillment steps.
Gain real‑time visibility into payments, orders, and fulfillment without writing code.
Definitions of endpoints, triggers, actions, and data fields used to integrate GHL with 46elks.
A credential used to authenticate requests between GHL and 46elks.
A URL endpoint that receives event notifications from the integration.
Endpoint to fetch and manage orders in the Payments API.
Delivery or shipment status updates and actions tied to orders.
Send automated SMS confirmations to customers when an order is created or updated.
Push status updates to customers through SMS or chat apps as soon as fulfillment happens.
Notify teams about refunds via instant messaging to speed resolution.
Create and securely store API keys in both GHL and 46elks.
Map endpoints for orders, fulfillments, and transactions to enable real-time sync.
Run tests, verify webhooks, and switch to production mode.
You authenticate with an API key or OAuth token. Generate credentials in both GHL and 46elks and store them securely. Rotate keys regularly, apply least‑privilege access, and restrict scopes to the endpoints you actually use.
End-to-end coverage includes orders, fulfillments, transactions, and subscriptions. Use GET /payments/orders/ to list orders, GET /payments/orders/:orderId/fulfillments for fulfillments, POST /payments/orders/:orderId/fulfillments to create fulfillments, and GET /payments/transactions/ for payments. Subscriptions endpoints provide recurring billing data with GET /payments/subscriptions/ and GET /payments/subscriptions/:subscriptionId.
Use a sandbox or test mode if available. Validate webhooks with test events and simulate orders and payments before going live. Review error responses and retry with backoff to ensure stability in production.
Register your webhook URL in the integration settings and verify the signature if provided. Test by triggering events like order created or fulfillment updated to confirm delivery of payloads.
Rate limits vary by endpoint; plan accordingly and implement exponential backoff on failures. Monitor quotas in the dashboard and optimize polling vs. webhook usage.
Implement retries with backoff, use idempotency keys where supported, and log errors for troubleshooting. Rely on webhook retry mechanisms if available to ensure reliability.
API documentation is available in the GHL developer docs and the 46elks API reference. Both provide endpoint details, authentication requirements, and example payloads.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
