Authenticate against GHL with the payments/integration.readonly scope to read orders, fulfillments and transactions. Use endpoints like GET /payments/orders, GET /payments/orders/:orderId and GET /payments/transactions/:transactionId to verify data before issuing certificates.
Configure Accredible Certificates as a connected app in GHL. Exchange keys securely, request tokens with the needed scopes, and rotate credentials on a schedule.
Examples include GET /payments/integrations/provider/whitelabel, POST /payments/integrations/provider/whitelabel, GET /payments/orders/, GET /payments/orders/:orderId, POST /payments/orders/:orderId/fulfillments, GET /payments/transactions/, and GET /payments/transactions/:transactionId.
Trigger: New or updated order data is detected.
Actions: Retrieve order details, validate payment status, and prepare certificate metadata for issuance.
Methods: GET /payments/orders/ and GET /payments/orders/:orderId
Key fields: orderId, status, totalAmount, customerEmail
Trigger: A fulfillment is created for an order.
Actions: Create or update an Accredible certificate and attach fulfillment data like certificateId.
Method path: POST /payments/orders/:orderId/fulfillments
Key fields: orderId, fulfillmentId, certificateId
Trigger: A new or updated transaction is recorded.
Actions: Log the transaction and reconcile with the certificate status.
Method path: GET /payments/transactions/ and GET /payments/transactions/:transactionId
Key fields: transactionId, amount, currency, status
Fast setup with ready made templates and mappings that work out of the box.
Automatic data synchronization between payments and certificates reduces manual work and errors.
Secure, auditable records with centralized access control and role management.
This glossary defines the core terms and processes used in the integration, including endpoints, authentication, data mapping, webhooks and error handling.
An API endpoint is a URL you call to retrieve or modify data, such as getting orders or creating fulfillments.
A webhook is a callback URL that the provider uses to notify your app about events like order fulfillment.
OAuth is a standard for authorization that lets apps access resources on behalf of a user.
A verifiable digital credential issued to a student or participant via Accredible.
Automatically generate and attach Accredible certificates when an order reaches fulfillment.
Aggregate transaction and fulfillment data to show live status in a central admin dashboard.
Create periodic reports of payments, fulfillments and certificates for compliance and insights.
Request a client_id and client_secret for the GHL API and register Accredible Certificates as an app.
Set scope to payments/integration.readonly and enable webhook events for fulfillments and transactions.
Run test payments, verify order status, and confirm certificate issuance in Accredible.
The Orders API exposes order, fulfillment, and payment data that you can map to Accredible certificate fields such as recipient, course, and completion date. You can filter by order status and payment status to ensure only eligible orders trigger certificates. Use GET /payments/orders/ and GET /payments/orders/:orderId to verify data before issuing a certificate. In practice, set up a data map that aligns orderId with certificateId and pulls the needed metadata from the order.
Webhooks notify your app when events occur, such as fulfillment or payment status changes. This enables real time certificate issuance without manual checks. Configure webhook endpoints to receive fulfillments and transactions events and trigger corresponding Accredible actions automatically.
If a payment is refunded, you should update the certificate status or revoke access as needed. The integration can detect refunds via transaction updates and apply business rules to certificate issuance and visibility. Maintain an audit trail for compliance.
You can implement many flows with no code using built in templates and webhooks, but basic scripting or a Zapier like connector can help customize field mappings and error handling. Most teams can start with no code and add light scripting later if needed.
Security requirements include using OAuth or token based authentication, least privilege scopes like payments/integration.readonly, secure key exchange, and rotating credentials regularly. Log access and monitor for unusual activity.
Yes. It is common to test in a sandbox environment first. Use test API keys, mock orders, and simulated fulfillments to validate data flows before going live.
Field mapping typically involves aligning orderId to certificateId, recipient name to the certificate holder, and fulfillment status to certificate status. Create a mapping document and test end to end to ensure fields populate correctly.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
