Learn how to securely authenticate GHL API requests from 97Display using tokens, OAuth, and best practices to protect credentials.
Configure your 97Display app to securely obtain and refresh access tokens, and to request only the permissions you need.
The integration uses key endpoints such as creating and updating contacts, retrieving campaigns, and managing tickets. Refer to the GHL API docs for the full endpoint list.
Trigger: New lead in 97Display creates or updates a contact in GHL
Actions: map fields, assign tags, add notes to the contact
POST /contacts
Key fields: email, firstName, lastName, phone
Trigger: Changes in 97Display campaigns update GHL campaigns
Actions: create or update campaigns, sync status and metrics
GET /campaigns
Key fields: id, name, status
Trigger: New 97Display support tickets create tasks in GHL
Actions: create tasks, update ticket status and comments
POST /tickets
Key fields: ticketId, subject, priority
Speedy setup with no coding required and a visual workflow builder
Real-time data syncing without custom development
Unified data across GHL and 97Display for better reporting
This glossary explains common terms used in the GHL API and 97Display integration so you can work faster.
Application Programming Interface; the set of rules that lets two applications communicate.
A real-time notification from the API that informs your system about events as they occur.
Open Authorization; a token-based method to securely grant access.
A specific URL in an API that performs a defined action or returns data.
Automatically push new leads from 97Display into GHL as contacts
Create GHL tickets from 97Display inquiries
Trigger GHL campaigns from events in 97Display
Obtain client ID, client secret, and redirect URI
Set up OAuth flow or API tokens and scopes
Run tests, validate data flow, and deploy securely
Answer part one for FAQ1. This integration is designed to work with no code for the most common tasks. You can connect 97Display to the GHL API using a simple setup wizard and prebuilt templates. If you need custom logic, you can extend the workflow with conditional steps. Answer part two for FAQ1. It is important to review permissions and scopes to ensure you access only what you need, keeping your data secure.
You can use this integration without Zapier by connecting directly via the GHL API endpoints from 97Display. Zapier remains an option for more complex automations if you want to layer apps together. If you prefer a no code path, rely on built in templates and connectors; for advanced flows you can combine multiple steps in 97Display and the GHL API.
Data that can sync includes contacts, campaigns, and tickets, along with associated fields like emails, names, statuses, and priorities. The exact mapping is configurable in the 97Display setup and respects the permissions granted to the GHL API. Notes: some fields require explicit scopes and may be limited by your GHL plan.
Requests are authenticated using OAuth tokens or API keys, depending on your configuration. Always keep credentials secure, rotate secrets periodically, and use scoped permissions to minimize access. In production, store tokens securely and refresh them automatically to prevent downtime.
Webhooks are supported to push real-time updates from GHL to 97Display and vice versa. They enable event-driven automation without polling. Be sure to configure webhook URLs, verify signatures, and handle retries gracefully. Testing webhooks in a staging environment helps prevent data integrity issues in production.
API documentation is available in the GHL developer portal and the 97Display integration docs. Review endpoint references, auth methods, rate limits, and example requests to accelerate your setup. If you need additional guidance, consult the support resources or request a developer walkthrough.
Security and data privacy are a priority. Use MFA where possible, restrict app permissions, and implement encryption in transit and at rest. Audit logs help track access and changes across GHL and 97Display.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
