Authenticate requests to the Orders API using OAuth 2.0 tokens or API keys. Store credentials securely in your GHL integration settings and rotate keys regularly.
To connect 17hats, obtain API credentials from your 17hats account and paste them into the GHL integration setup to establish a trusted link.
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
Trigger when a payment is completed in 17hats to create or update a corresponding payment in the Orders API.
GET /payments/integrations/provider/whitelabel; POST /payments/integrations/provider/whitelabel
orderId, providerId, paymentStatus
Trigger when an 17hats order is updated to fulfilled to create or update fulfillments in the Orders API.
Create fulfillments, update shipment status, and reflect changes back to 17hats.
GET /payments/orders/; GET /payments/orders/:orderId/fulfillments; POST /payments/orders/:orderId/fulfillments
orderId, fulfillmentId, status
Trigger on new transactions or subscription changes to keep 17hats invoices and billing current.
Sync transactions and subscriptions between both systems.
GET /payments/transactions/; GET /payments/subscriptions/
transactionId, subscriptionId
Automate routine tasks without writing a line of code
Live data across payments, orders, and fulfillments for faster decisions
Simple setup, easy maintenance, and scalable workflows
A quick glossary covering API endpoints, payloads, authentication, webhooks, and data mapping used in this integration.
A defined URL that performs an action via the API.
Verifying identity using API keys, OAuth, or tokens.
A real-time listener for events from an API.
The data sent with a request or returned in a response.
Automatically push payment status from the Orders API to 17hats when a payment is completed.
Sync shipment events to create or update fulfillments in 17hats automatically.
Auto-create invoices in 17hats when a payment is confirmed in the Orders API.
Get your API keys from 17hats and add them to the GHL connection settings.
Set up event listeners for payments, orders, and transactions.
Run tests and activate the integration in production.
No dedicated developer account is required. Use the API credentials provided in your 17hats account and configure them in the GHL integration settings to establish the connection. If you need advanced customization, reach out to support for guidance. In most setups, the built-in connectors suffice for standard sync tasks.
For a standard sync, focus on payments, orders, fulfillments, and transactions endpoints. Map order IDs between platforms and keep statuses aligned. Use webhooks to receive real-time updates and minimize polling.
If a payment fails, capture the failure reason from the Orders API and trigger a retry or notify the relevant team in 17hats. Maintain clear status fields and provide a backoff strategy to avoid repeated failures.
Yes. Webhooks can be customized to listen for specific events (e.g., payment succeeded, order fulfilled). In your GHL settings, filter events and route them to appropriate actions in 17hats.
Rate limits depend on the API plan. Monitor usage via headers and implement exponential backoff for retry logic to remain within limits while ensuring reliable processing.
API credentials are generated in the 17hats account and then pasted into the GHL integration setup. Securely store keys, rotate them periodically, and revoke access if credentials are compromised.
Yes. You can disconnect and reconnect the integration from the GHL dashboard. Re-authenticate with fresh credentials as needed and verify that all mappings are intact after reconnecting.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
