Access requires secure authentication via GHL with API key and OAuth scopes for read access to contacts data.
MSG91 uses API keys and OAuth tokens to authorize requests. Keep credentials secure and rotate keys regularly. The scope for this page is contacts.readonly.
GET /contacts/:contactId; GET /contacts/:contactId/tasks; GET /contacts/:contactId/tasks/:taskId; GET /contacts/:contactId/notes; GET /contacts/:contactId/notes/:id; GET /contacts/:contactId/appointments; GET /contacts/; GET /contacts/business/:businessId; POST /contacts/; PUT /contacts/:contactId; DELETE /contacts/:contactId; POST /contacts/:contactId/tasks; PUT /contacts/:contactId/tasks/:taskId; PUT /contacts/:contactId/tasks/:taskId/completed; DELETE /contacts/:contactId/tasks/:taskId; POST /contacts/:contactId/tags
Trigger: a request to fetch a contact in MSG91 initiates a pull of data from GHL
Actions: GET /contacts/:contactId; GET /contacts/:contactId/tasks; GET /contacts/:contactId/notes
GET /contacts/:contactId
Key fields: contactId, name, email
Trigger: new or updated contact in MSG91
Actions: POST /contacts/; POST /contacts/:contactId/tasks
POST /contacts/
Key fields: contactId, firstName, lastName, phone
Trigger: notes updated in MSG91
Actions: PUT /contacts/:contactId/notes; POST /contacts/:contactId/tags
PUT /contacts/:contactId/notes
Key fields: contactId, noteId, content
Build a working integration with no code using drag and drop automations
Sync data across MSG91 and GHL to reduce manual entry
Speed onboarding with ready made templates and workflows
This glossary covers API, endpoint, authentication, webhook and data fields used in the MSG91 and Contacts API integration with GHL
An interface that lets software interact with a service
A URL path that performs a specific operation in an API
The process of granting permission to access resources
A callback URL that receives events from an API
Automatically provision a MSG91 contact into GHL with initial tags
Create tasks in MSG91 and mirror them in GHL for follow ups
Sync notes and tags between MSG91 and GHL for richer context
Collect MSG91 API keys and OAuth tokens and configure in GHL as the Contacts API
Map MSG91 endpoints to GHL actions starting with GET /contacts/:contactId
Run tests, verify data flow and enable automations
MSG91 needs read access to Contacts data in GHL. Use a dedicated API key and limit the scope to contacts.readonly to minimize risk. Assign appropriate roles and store keys securely.
No heavy coding is required. You can leverage prebuilt actions and webhooks in GHL to map MSG91 endpoints. For advanced flows you may add lightweight scripts.
Essential endpoints for a basic setup include GET /contacts/:contactId, GET /contacts/, and POST /contacts/. Start with retrieving a contact and creating a new one.
Yes. You can sync notes and tags by mapping MSG91 notes to GHL notes and MSG91 tags to GHL tags in your automations.
Authenticate requests using API keys and OAuth tokens. Rotate credentials regularly and use secure storage.
Run test requests against the endpoints, check responses, and verify data is correctly echoed in GHL. Use sample contacts for validation.
Endpoint documentation is available in the page sections and sample endpoint list, plus a complete set of endpoints in the MSG91 integration docs.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
