> For the complete documentation index, see [llms.txt](https://whatsnap.gitbook.io/whatsnap-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://whatsnap.gitbook.io/whatsnap-docs/faq/general/api-integrations.md).

# Do You Have an API?

Learn about WhatSnap's integration capabilities, GoHighLevel deep integration,  and options for connecting with other platforms.

## Current Status: No Public API

WhatSnap does **not currently have an open public API** for direct integration.

However, WhatSnap provides **deep native integration with GoHighLevel** that covers most use cases, including workflows, webhooks, and automation capabilities.

{% hint style="info" %}
**GoHighLevel Integration**: WhatSnap is specifically designed as a GoHighLevel plugin with deep platform integration. This provides more functionality than a standard API for GHL users.
{% endhint %}

***

## Deep GoHighLevel Integration

### What WhatSnap Integrates With

WhatSnap seamlessly integrates with multiple GoHighLevel systems:

#### 1. **Conversation System**

* All messages (WhatsApp, SMS, iMessage) appear in GHL conversations
* Unified inbox across all platforms
* Team collaboration on conversations
* Message history and tracking
* Conversation assignment and routing

#### 2. **Workflow Automation**

* Send messages from GHL workflows
* Trigger workflows from incoming messages
* Use conditional logic based on message content
* Wait for reply actions
* Tag-based routing in workflows

#### 3. **Contact Management**

* Automatic contact creation from incoming messages
* Tag assignment for account routing
* Custom field population
* Contact segmentation
* DND (Do Not Disturb) management

#### 4. **Campaign System**

* Bulk messaging campaigns
* Contact list targeting
* Message personalization
* Drip campaign scheduling
* A/B testing variants

#### 5. **Webhook System**

* Incoming message webhooks
* Outgoing message status webhooks
* Delivery confirmation events
* Read receipt events (WhatsApp)
* Contact creation events

***

## Integration Capabilities

### What You Can Do Without an API

**Messaging Features:**

* ✅ Send messages from GHL workflows
* ✅ Send messages from GHL conversations
* ✅ Send bulk campaigns from GHL
* ✅ Receive messages into GHL conversations
* ✅ Send attachments (images, videos, documents)
* ✅ Schedule messages through GHL

**Automation:**

* ✅ Workflow-based automation
* ✅ Webhook-based automation
* ✅ Trigger-based messaging
* ✅ Conditional logic flows
* ✅ Wait for reply actions
* ✅ Tag-based routing

**Data & Tracking:**

* ✅ Message history in GHL
* ✅ Delivery status tracking
* ✅ Contact activity tracking
* ✅ Campaign performance analytics
* ✅ Response rate tracking

**Multi-Platform:**

* ✅ WhatsApp messaging
* ✅ SMS messaging (P2P)
* ✅ iMessage support
* ✅ Twilio SMS integration
* ✅ Tag-based platform selection

***

## Use Cases Covered by GHL Integration

### ✅ Covered Use Cases (No API Needed)

**1. Automated Follow-Ups**

* Use GHL workflows to send timed follow-ups
* Trigger messages based on contact actions
* Personalize with custom fields
* Works across all platforms (WhatsApp, SMS, iMessage)

**2. Lead Nurturing**

* Drip campaigns through GHL
* Behavior-based messaging
* Tag-based segmentation
* Multi-step sequences

**3. Appointment Reminders**

* Calendar integration with GHL
* Automated reminder workflows
* Confirmation requests
* Rescheduling automation

**4. Customer Service**

* Team inbox for incoming messages
* Conversation assignment
* Internal notes and collaboration
* Response templates

**5. Broadcast Campaigns**

* Mass messaging to contact lists
* Message variants and personalization
* Scheduled send times
* Performance tracking

**6. Webhook Integration**

* Receive incoming messages via webhook
* Process with external systems (Zapier, Make, n8n)
* Trigger external workflows
* Custom integrations via webhooks

***

### ❌ Use Cases Requiring an API

**These scenarios are NOT currently possible:**

**1. Direct Integration with Non-GHL Platforms**

* Custom CRM systems (outside GHL)
* E-commerce platforms (Shopify, WooCommerce)
* Custom applications
* Third-party automation tools (without webhook workarounds)

**2. Programmatic Account Management**

* Automated account creation
* Bulk device configuration
* Custom dashboard creation
* Reporting API access

**3. Advanced Customization**

* Custom message routing logic (beyond tags)
* Custom delivery algorithms
* Advanced analytics extraction
* White-label API access

***

## Workarounds for API Limitations

### Using Webhooks as an Alternative

WhatSnap supports webhooks for many automation scenarios:

**Incoming Message Webhook:**

1. Configure webhook URL in GHL workflow
2. Receive incoming message data
3. Process with external service (Zapier, Make, n8n, custom server)
4. Send response back through GHL workflow action

**Outgoing Message Webhook:**

1. Use GHL API to create contact and send message
2. WhatSnap delivers message
3. Receive delivery status via webhook
4. Process confirmation in external system

**Example Webhook Flow:**

```
External System (e.g., Shopify)
    ↓
Webhook to GHL API (create contact + message)
    ↓
GHL Workflow (trigger WhatSnap send)
    ↓
WhatSnap sends message (WhatsApp/SMS)
    ↓
Delivery webhook back to external system
    ↓
Confirmation processed
```

***

### Using Zapier/Make/n8n

**Popular Integration Platforms:**

* **Zapier**: Connect 5,000+ apps to GHL
* **Make (formerly Integromat)**: Visual automation builder
* **n8n**: Open-source workflow automation

**How It Works:**

1. **Trigger**: Event in external app (e.g., new Shopify order)
2. **Action**: Use GHL API to create contact and send message
3. **WhatSnap**: Automatically sends message via connected account
4. **Result**: Message delivered through WhatSnap platform

**Example Integrations:**

**E-commerce Order Confirmation:**

```
Shopify → Zapier → GHL API → WhatSnap → WhatsApp Customer
```

**Support Ticket Creation:**

```
WhatSnap → GHL Webhook → Make → Zendesk → Create Ticket
```

**CRM Sync:**

```
External CRM → n8n → GHL API → WhatSnap → Send Message
```

***

### Using GoHighLevel API

**GHL provides a robust API** for managing contacts, workflows, and conversations.

**Common Patterns:**

**Send Message via API:**

```javascript
// Example: Send message through GHL API
// WhatSnap automatically handles delivery

const message = {
  contactId: "contact_123",
  message: "Hello from API!",
  type: "SMS" // or WhatsApp based on contact tag
};

// GHL API call
fetch('https://rest.gohighlevel.com/v1/conversations/messages', {
  method: 'POST',
  headers: {
    'Authorization': 'Bearer YOUR_API_KEY',
    'Content-Type': 'application/json'
  },
  body: JSON.stringify(message)
});

// WhatSnap automatically delivers via appropriate account
```

**Receive Webhook:**

```javascript
// Example: Receive incoming message webhook

app.post('/webhook/incoming', (req, res) => {
  const message = req.body;
  
  console.log('From:', message.contactId);
  console.log('Message:', message.body);
  console.log('Platform:', message.source); // WhatsApp, SMS, etc.
  
  // Process message and respond
  // Can trigger external actions, AI processing, etc.
  
  res.status(200).send('OK');
});
```

***

## Requesting Platform Integrations

### We're Focused on GoHighLevel

WhatSnap is currently focused on providing the **best possible integration with GoHighLevel** and expanding features within that ecosystem.

**Our Priorities:**

1. ✅ **Deep GHL integration** - Maximize functionality within GHL
2. ✅ **Multi-platform support** - WhatsApp, SMS, iMessage, Twilio
3. ✅ **Campaign features** - Bulk messaging, variants, scheduling
4. ✅ **Reliability** - Stable connections, high deliverability
5. ✅ **Ease of use** - Simple setup, intuitive interface

***

### Want to Request an Integration?

**If you need integration with another platform:**

**Option 1: Use Webhooks + Integration Platforms**

* Connect via Zapier, Make, or n8n
* Use GHL API as intermediary
* Most use cases can be covered this way

**Option 2: Request a Feature**

* Email: <support@whatsnap.ai>
* Subject: "Integration Request: \[Platform Name]"
* Include:
  * Platform you want to integrate
  * Your use case
  * Expected message volume
  * Why GHL webhooks won't work
  * Number of users who would benefit

**We Evaluate Requests Based On:**

* Number of user requests
* Technical feasibility
* Alignment with WhatSnap's vision
* Development resources required
* Market demand

{% hint style="info" %}
**Most Popular Requests Get Priority**: If many users request the same integration, it's more likely to be developed. Make sure to submit your request!
{% endhint %}

***

## Roadmap: Future API Plans

### Potential Future Developments

While we don't have a public API now, we're considering:

**Possible Future Features:**

* 🔮 Public REST API for developers
* 🔮 Webhook enhancements
* 🔮 Additional platform integrations
* 🔮 Advanced reporting API
* 🔮 White-label API access

{% hint style="warning" %}
**No Timeline**: These are potential future features with no confirmed timeline. Current focus is on GoHighLevel integration excellence.
{% endhint %}

***

## Working Within Current Capabilities

### Best Practices

**1. Leverage GHL Workflows**

* Most automation needs can be met with GHL workflows
* Use conditional logic extensively
* Combine multiple workflow triggers
* Use tags for sophisticated routing

**2. Use Webhooks Extensively**

* Configure webhooks for incoming messages
* Process data externally if needed
* Send responses back through GHL API
* Build custom logic outside WhatSnap

**3. Combine with Integration Platforms**

* Zapier for simple automations
* Make for complex visual workflows
* n8n for open-source self-hosted option
* GHL API as the bridge

**4. Plan Around Tag System**

* Use tags for account routing
* Use tags for workflow logic
* Use tags for segmentation
* Creative tag usage can replace many API needs

***

## Comparison: WhatSnap vs. API-First Platforms

### Different Philosophy

**API-First Platforms (like Twilio):**

* ✅ Flexible, programmatic control
* ✅ Build custom solutions
* ⚠️ Requires developer resources
* ⚠️ Complex setup and maintenance
* ⚠️ Steeper learning curve

**WhatSnap (Integration-First):**

* ✅ No-code/low-code approach
* ✅ Native GHL integration
* ✅ Fast setup (minutes)
* ✅ Non-technical friendly
* ⚠️ Limited to GHL ecosystem

**Best For:**

**Choose API-First (Twilio) If:**

* You have development resources
* Need complete programmatic control
* Building custom application
* Want platform independence

**Choose WhatSnap If:**

* You use GoHighLevel
* Want fast, simple setup
* Don't need custom development
* Prefer no-code automation
* Want multi-platform (WhatsApp + SMS + iMessage)

***

## Summary: WhatSnap Integration Capabilities

**No Public API, But Rich Integration:**

**✅ What's Available:**

* Deep GoHighLevel integration
* Workflow automation
* Webhook support
* GHL API compatibility
* Multi-platform messaging (WhatsApp, SMS, iMessage, Twilio)
* Campaign and bulk messaging

**❌ What's Not Available:**

* Public REST API
* Direct platform-to-platform integration (outside GHL)
* Programmatic account management
* Custom white-label API

**🔄 Workarounds:**

* Use GHL API + webhooks
* Integrate via Zapier/Make/n8n
* Leverage GHL workflow automation
* Creative use of tags and routing

**🔮 Future:**

* Focused on GHL integration excellence
* Considering future API development
* Open to integration requests
* No confirmed timeline for public API

{% hint style="success" %}
**For Most Users**: GHL integration is more than sufficient for automation, campaigns, and messaging workflows. The deep platform integration provides more value than a basic API for GHL users.
{% endhint %}

***

## Getting Started with WhatSnap Integration

{% stepper %}
{% step %}

#### Install WhatSnap Plugin

[Follow the Quick Start Guide](/whatsnap-docs/quick-start.md) to install WhatSnap in your GoHighLevel account.
{% endstep %}

{% step %}

#### Connect Messaging Accounts

Choose your platforms:

* [WhatsApp](/whatsnap-docs/account-management/whatsapp.md) - Instant setup
* [SMS/iMessage](/whatsnap-docs/account-management/sms/sms-installation-setup.md) - Device setup
* [Twilio](/whatsnap-docs/account-management/twilio.md) - Enterprise SMS
  {% endstep %}

{% step %}

#### Set Up Workflows

Create automated messaging workflows in GHL:

* [Workflow Automation Guide](/whatsnap-docs/conversations/workflow-automation.md)
* [Messaging Basics](/whatsnap-docs/conversations/messaging-basics.md)
  {% endstep %}

{% step %}

#### Configure Webhooks (Optional)

If you need external integrations:

* Set up incoming message webhooks in GHL
* Configure outgoing message status webhooks
* Connect to Zapier/Make/n8n for external processing
  {% endstep %}
  {% endstepper %}

***

## Related Resources

* [Quick Start Guide](/whatsnap-docs/quick-start.md) - Get started with WhatSnap
* [Workflow Automation](/whatsnap-docs/conversations/workflow-automation.md) - Automate messaging
* [Account Management](/whatsnap-docs/account-management.md) - Multi-account setup
* [Campaign Overview](/whatsnap-docs/outreach/campaign-overview.md) - Bulk messaging

***

**Have integration questions?** Contact <support@whatsnap.ai> to discuss your specific use case and find the best solution within WhatSnap's current capabilities.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://whatsnap.gitbook.io/whatsnap-docs/faq/general/api-integrations.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.