Frequently Asked Questions

Everything you need to know about OpenWA, our features, and how to get started.

About OpenWA

OpenWA is a free, open-source WhatsApp API gateway designed for developers who need full control over their messaging infrastructure without vendor lock-in or hidden paywalls. It provides a powerful REST API, a modern web dashboard, and a pluggable architecture to build custom WhatsApp applications.

OpenWA is perfect for developers, startups, and businesses that want to integrate WhatsApp into their applications without the restrictions and costs of official APIs. It's ideal for building chatbots, customer service tools, notification systems, internal communication platforms, and more. It's particularly popular among AI developers, e-commerce platforms, and team collaboration tools.

Yes, OpenWA is 100% open source. It's released under the MIT License, which means you can use it for personal or commercial projects without any licensing fees. You have full access to the source code, allowing you to customize, extend, and audit the software to meet your specific needs.

The main difference is that OpenWA is an unofficial gateway that connects to WhatsApp through reverse-engineered clients, while the official WhatsApp Cloud API is a sanctioned service from Meta. OpenWA offers more flexibility, advanced features like message editing and reactions, and avoids vendor lock-in. However, the official API is more stable and has a lower risk of account restrictions. OpenWA is better for internal tools, personal projects, and applications where you can accept the inherent risks.

Getting Started

Getting started with OpenWA is easy and can be done in minutes:

  1. Deploy OpenWA using Docker (recommended) or access our web application
  2. Create a new session in the dashboard
  3. Scan the QR code with your WhatsApp mobile app to authenticate
  4. Generate API keys for your applications
  5. Start building with our REST API or webhooks

OpenWA is designed to be deployed easily in various environments:

  • Docker: The recommended method using our pre-built images for zero-config setup
  • Web Application: Access it directly through your browser at openwa.apposters.com/app
  • Cloud Platforms: Deploy on AWS, Google Cloud, Azure, or other cloud providers
  • On-Premise: Run it on your own servers for maximum control

It depends on how you want to use it. The web dashboard is designed to be user-friendly and requires no coding knowledge for basic tasks like managing sessions and viewing messages. However, to build custom applications, you'll need programming skills to work with our REST API. We provide comprehensive documentation and examples to help developers get started.

Features & Functionality

OpenWA provides a comprehensive set of messaging features:

  • Send and receive text messages
  • Send and receive media (images, videos, documents, audio)
  • Message reactions with emoji
  • Message editing and live edited events
  • Bulk messaging to multiple recipients
  • Message status tracking (delivered, read)
  • Group creation and management
  • Profile management (name, about, photo)
  • WhatsApp Channels support
  • Labels for chat organization

Yes, OpenWA is built to handle multiple WhatsApp sessions concurrently. You can run several WhatsApp accounts on a single instance, each with its own independent session, API keys, and webhooks. This makes it perfect for managing business and personal accounts, or for running multiple chatbots simultaneously.

API key scoping is a powerful security feature that allows you to limit what each API key can access:

  • Session Scoping: Restrict an API key to specific WhatsApp sessions
  • Chat Scoping: Further restrict an API key to specific chats (groups and contacts)
  • Role-based Access: Create operator (full access) or viewer (read-only) keys
  • IP Whitelisting: Restrict API keys to specific IP addresses

This is essential for multi-tenant applications, shared accounts, and ensuring agents can only access their designated conversations.

Webhooks allow OpenWA to send real-time events to your application whenever something happens in WhatsApp. You can configure webhooks to send notifications for events like:

  • New messages received
  • Message status changes (delivered, read)
  • Session connection status changes
  • Group events (added, removed, left)

Webhooks include HMAC signatures for security and support smart filters to only trigger events that match specific conditions (e.g., only messages from certain contacts).

Security & Compliance

Yes, there is always a non-zero risk of account restriction or ban. OpenWA connects to WhatsApp through unofficial, reverse-engineered clients, which violates WhatsApp's Terms of Service. While we've implemented best practices to minimize risk, we cannot eliminate it entirely.

To reduce risk:

  • Never use your primary personal or business number
  • Use a dedicated number you can afford to lose
  • Warm up new numbers gradually before heavy automation
  • Avoid cold-blasting strangers
  • Use rate limiting and stay within reasonable sending limits
  • Use opted-in recipients for safest messaging

We offer two engines with different risk profiles:

  • whatsapp-web.js: Lower risk - drives a real headless Chromium that mimics genuine WhatsApp Web traffic. Higher RAM usage (~300-500MB per session).
  • baileys: Higher risk - speaks the multi-device WebSocket protocol directly and is easier for WhatsApp to fingerprint. Lower RAM usage (~30-80MB per session).

If account safety is your top priority and you can afford the memory, prefer whatsapp-web.js.

OpenWA provides flexible storage options with security in mind:

  • Databases: Choose between SQLite (simple) or PostgreSQL (production-grade)
  • Media Storage: Store media locally or use S3/MinIO for cloud storage
  • Caching: Optional Redis for performance
  • Encryption: API keys are hashed, sensitive data is protected
  • Container Security: Runs as a non-root user with proper isolation

Message media is returned inline to API and webhook consumers by default; it is not automatically persisted to storage unless you configure it.

For any deployment where ethical, legal, or regulatory compliance matters (healthcare, finance, large-scale commercial messaging, anything touching end users in the EU/EEA under DMA/GDPR framings), you should treat OpenWA as not approved and use Meta's official WhatsApp Cloud API instead. OpenWA is an excellent fit for personal projects, internal tooling, automation hobbyists, and learning—it is not a drop-in replacement for the official API in regulated environments.

Plans & Pricing

OpenWA is completely free and open source. There are no licensing fees, subscription costs, or hidden charges. You can use it for personal projects, commercial applications, and everything in between without paying anything. The only costs would be for your own hosting infrastructure if you choose to self-host.

OpenWA itself doesn't enforce hard usage limits. However, we recommend implementing rate limiting to avoid triggering WhatsApp's anti-abuse systems. The software includes configurable rate limiting settings that you can adjust based on your needs. Remember that regardless of technical limits, you should always follow our safe-sending guidelines to minimize the risk of account restrictions.

Support & Community

As an open-source project, OpenWA offers community-based support:

  • Documentation: Comprehensive guides and API reference
  • Community Forum: Connect with other users and developers
  • GitHub Issues: Report bugs and request features
  • Discord/Slack: Real-time chat with the community

For enterprise customers who need dedicated support, we offer premium support packages with guaranteed response times and custom development services.

We welcome contributions from the community! You can help OpenWA in many ways:

  • Report bugs and suggest new features
  • Improve documentation and examples
  • Translate the interface or documentation
  • Build plugins and integrations
  • Share your success stories and use cases
  • Help other users in the community forum

For developers interested in contributing code, please review our documentation and follow the established coding standards.

If you need help with OpenWA, here are the best resources:

  • Documentation: Start with our comprehensive docs at openwa.apposters.com/docs
  • FAQ: Check this page for common questions and answers
  • Community: Join our community forum for peer support
  • GitHub Issues: Search existing issues or create a new one
  • Discord/Slack: Join our community chat for real-time help

Still Have Questions?

Our community and documentation are here to help you get the most out of OpenWA