Messaging FAQs

UMVA Messaging is a business messaging platform that provides WhatsApp Business API and Email API access. Unlike traditional providers, we offer no KYC, no template verification, no per-message fees — just a flat $5/month per platform with unlimited sending. Launching in 2025, we are redefining what business messaging should look like.

No. No KYC (Know Your Customer) verification is required. You can start using WhatsApp and Email APIs immediately without uploading any identification documents or providing personal information. Simply sign up, subscribe, and start sending messages.

No. Unlike official WhatsApp Business API providers, we do not require template approval from Meta. You can send any message, anytime, without template submission. No review process, no rejection nightmares — just unrestricted messaging.

Signing up is quick and straightforward. Create an account on our platform, choose your desired messaging subscription (WhatsApp API, Email API, or both), complete payment, and you are ready to start sending. No lengthy verification processes or approval waiting periods.

Simply scan the QR code from your dashboard to link your WhatsApp number. The process takes seconds. Once connected, you can start sending and receiving messages through our API. Multi-device support allows you to keep your phone connected simultaneously.

Yes. You can add or remove platform subscriptions at any time from your messaging dashboard. Upgrade from a single platform to both, or downgrade as your needs change. All changes take effect immediately with no setup fees.

We offer a limited free trial that allows you to test the platform before committing to a subscription. The trial includes a restricted number of messages so you can evaluate the API, check deliverability, and ensure UMVA Messaging meets your requirements.

From your messaging dashboard, click the Connect WhatsApp button to generate a QR code. Open WhatsApp on your phone, tap the three-dot menu (Android) or Settings (iOS), select Linked Devices, then Link a Device, and scan the QR code displayed on your dashboard. Your number is connected instantly.

Yes, WhatsApp multi-device is fully supported. You can connect your WhatsApp number through our API while keeping your phone and other linked devices active simultaneously. Multi-device ensures messages sync across all connected devices without requiring your phone to maintain an active internet connection.

Your WhatsApp number must be an active WhatsApp account registered on your phone. It can be tied to either a SIM card or a VoIP number, as long as it can receive the initial verification. The number must not be banned or restricted by WhatsApp. Standard business or personal WhatsApp accounts both work.

Absolutely. You can connect your existing personal WhatsApp number to UMVA Messaging. Your personal chats and group conversations remain unaffected. The API operates alongside your normal WhatsApp usage, giving you access to programmatic sending and receiving without changing your primary messaging experience.

Yes, you can connect multiple WhatsApp numbers to a single UMVA Messaging account. Each subscription covers one WhatsApp number. If you need multiple numbers — for different brands, departments, or regions — simply subscribe to additional WhatsApp API subscriptions and connect each number individually.

WhatsApp sessions can expire if the phone loses internet connectivity for an extended period or if you log out from the linked devices page. If your session expires, you will receive a notification in your dashboard. Simply re-scan the QR code to re-establish the connection. No messages are lost during this time.

Yes. Your WhatsApp number is linked via an encrypted session, and we never store your WhatsApp credentials or messages on our servers beyond what is needed to deliver the service. Your connection is secured end-to-end, and you can revoke API access at any time by unlinking the device from your WhatsApp settings.

You can send text messages, images (JPEG, PNG, WebP), videos (MP4, AVI, MOV), audio files (MP3, OGG, WAV), documents (PDF, DOCX, XLSX, PPTX), sticker images, contact cards (vCard), and location pins. Each message type has a dedicated API endpoint with appropriate media handling.

Yes, the WhatsApp API fully supports media attachments. You can send images, videos, audio clips, and documents of various formats. Media files can be uploaded directly via URL or base64-encoded data. There is a per-file size limit of 64 MB for videos and 16 MB for other media types.

No. Unlike official WhatsApp Business API providers, UMVA Messaging does not require Meta-approved message templates. You can send any message content freely — no template submission, no approval waiting, no content restrictions. This applies to all message types including marketing and promotional messages.

Yes, you can send bulk messages to thousands of recipients. The API supports sending to multiple phone numbers in a single request via our broadcast endpoint. There are no daily sending limits, so you can run large-scale campaigns without throttling. For best deliverability, we recommend implementing reasonable pacing between batches.

There are no hard daily rate limits. However, to maintain connection stability and avoid temporary blocks from WhatsApp, we recommend sending at a moderate pace — approximately 10–20 messages per second for most accounts. Higher throughput is available on request. The API provides rate-limit headers to help you manage your sending pace.

Yes, the API supports sending messages to WhatsApp groups if you are a member of the group. You can send text, media, and files to groups using the group ID or phone number with the group invite link. You can also programmatically retrieve group participant lists and manage group settings.

Yes, you can send messages to WhatsApp channels that you own or follow. The API allows you to post updates, media, and rich content to your channel audience. Channel messages can be text, images, or videos, and they appear as broadcast updates visible to all channel subscribers.

Incoming WhatsApp messages are received via webhooks. Configure a webhook URL in your dashboard, and every incoming message sent to your connected WhatsApp number will be forwarded to your endpoint as a JSON payload in real time. The payload includes sender information, message content, media details, and timestamps.

When a contact sends a message to your WhatsApp number, our server sends an HTTP POST request to your configured webhook URL with the full message payload. You must return a 200 OK response to acknowledge receipt. If your endpoint is unavailable, we retry delivery up to five times with exponential backoff. Webhooks can be tested from your dashboard.

Yes, you can build powerful chatbots by combining incoming webhooks with the send message API. When a webhook delivers an incoming message, your application processes it — using keyword matching, AI/NLP, or decision trees — and responds via the API. This enables automated customer support, lead qualification, order updates, and FAQ bots.

Auto-reply allows you to automatically respond to incoming messages based on rules you define. Set up keyword triggers, regex patterns, or catch-all responses from your dashboard or via the API. Auto-replies can include text, media, or interactive elements. You can enable auto-reply mode globally or for specific contacts.

Yes, the API provides endpoints to fetch your chat history, including incoming and outgoing messages. You can retrieve messages by date range, contact, or conversation ID. This is useful for building custom dashboards, exporting conversation logs, or syncing chats with your CRM or helpdesk system.

Our Email API provides SMTP relay and REST API access for sending emails. You get unlimited sending with no daily caps. Features include delivery analytics, open/click tracking, and support for attachments and HTML content. Simply configure your application with our SMTP credentials or use our REST endpoints to send transactional and marketing emails.

SMTP is the traditional email protocol ideal for legacy applications, email clients, and CMS platforms like WordPress that support SMTP plugins. Our REST API is better for modern applications, offering JSON-based requests, synchronous responses with delivery status, attachment handling, and easier integration with web frameworks. Both methods offer the same deliverability and unlimited sending.

Yes. You can configure custom sending domains with SPF, DKIM, and DMARC authentication to ensure high deliverability. Our setup wizard guides you through the DNS configuration process step by step. Using your own domain improves inbox placement and prevents your emails from being marked as spam.

From your messaging dashboard, navigate to the Email API settings and select your sending domain. We will generate unique DKIM key and SPF record values for your domain. Add these as DNS TXT records with your domain registrar or DNS hosting provider. Once DNS propagation completes (usually within minutes to hours), we automatically verify and enable authentication for your domain.

Deliverability depends on your sending reputation and domain authentication. We maintain high-IP reputation across our sending infrastructure. To maximize inbox placement, configure SPF, DKIM, and DMARC for your sending domain, maintain good sending practices (low bounce rates, relevant content), and warm up new domains gradually. Our analytics dashboard provides real-time delivery metrics.

Our analytics dashboard shows real-time metrics including total sent, delivered, opened, clicked, bounced, and spam-reported emails. You get per-message tracking with unique open and click tracking pixels. Detailed logs show delivery status, SMTP response codes, and timestamps. Data is retained for 90 days and can be exported as CSV or JSON.

Yes. We provide IMAP access for reading live emails, allowing you to build inbound email processing workflows. Connect any IMAP-compatible client or library to fetch incoming emails programmatically. This is perfect for support ticket systems, email parsing, automated email responses, and building custom email-to-SMS or email-to-webhook workflows.

Yes, transactional emails are fully supported and are an ideal use case for our Email API. Send password resets, order confirmations, welcome emails, invoice notifications, two-factor authentication codes, and any other system-generated emails. Our REST API allows you to send transactional emails with dynamic content, attachments, and custom headers.

UMVA Messaging costs just $5/month per platform. WhatsApp API is $5/month and Email API is $5/month. There are no per-message fees, no overage charges, and no hidden costs. You pay one flat fee and send unlimited messages. No metering, no surprises — just predictable pricing every month.

No. Unlike Twilio, 360dialog, MessageBird, SendGrid, and other providers that charge per message, we never charge per message. Send unlimited messages for a single flat monthly fee. Whether you send 100 messages or 10 million, the price stays the same. No overage charges, no tier upgrades, no usage caps.

There are no monthly sending limits, so you will never be capped or throttled. Send as many messages as you need, every single month, for the same flat $5/month per platform. No warning emails about hitting your limit, no automatic upgrades to higher-priced plans, no surprise charges on your bill.

Yes. You can subscribe to both WhatsApp and Email APIs on a single account. You can also add multiple WhatsApp number subscriptions if you need to manage several phone numbers. Each subscription is billed separately at $5/month. Your dashboard displays all active subscriptions, usage, and billing in one unified view.

Yes, you can downgrade or cancel any subscription at any time from your billing settings. When you cancel, your subscription remains active until the end of the current billing period. No cancellation fees, no long-term contracts, and no questions asked. Your data is retained for 30 days after cancellation in case you decide to reactivate.

We accept Visa, Mastercard, American Express, and Verve cards, plus cryptocurrency payments including USDT (ERC-20, TRC-20, BEP-20), USDC, Bitcoin (BTC), and Ethereum (ETH). All prices are listed in USD. Card payments are processed securely through our payment gateway, and crypto payments are credited instantly on the blockchain.

Yes, n8n integration is fully supported. Use our REST API nodes in n8n to build complex automation workflows connecting WhatsApp and Email APIs with hundreds of other services. Trigger WhatsApp messages from database changes, auto-reply to incoming emails, sync contacts between platforms — all without writing code. Pre-built workflow templates are available.

Yes, we provide a dedicated Make integration module. You can connect WhatsApp and Email API actions directly in your Make scenarios. Common use cases include sending WhatsApp notifications when a new row appears in Google Sheets, forwarding form submissions via WhatsApp, and creating email-to-WhatsApp bridges for customer communication.

Yes, UMVA Messaging is available on Zapier. Connect WhatsApp and Email APIs with thousands of Zapier-supported apps including Gmail, Slack, Shopify, HubSpot, Salesforce, WordPress, Google Sheets, and more. Triggers and actions are available for incoming messages, sending messages, email delivery events, and webhook-based automations.

We provide official SDKs for PHP, Python, and Node.js to simplify integration. Each SDK includes methods for all API endpoints, automatic error handling, rate-limit awareness, and typed request/response models. Community-supported wrappers are also available for Java, Go, Ruby, and C#. Our REST API is compatible with any language that supports HTTP requests.

Authentication is handled via API keys. From your messaging dashboard, generate an API key with the appropriate permissions (send, receive, or admin scope). Include the API key in the Authorization header of every HTTP request: Authorization: Bearer your_api_key_here. API keys can be rotated or revoked at any time from your dashboard.

The API returns standard HTTP status codes: 200 for success, 400 for bad requests, 401 for authentication errors, 404 for not found, 429 for rate limiting, and 500 for server errors. Each error response includes a descriptive message and an error code. We recommend implementing exponential backoff retry logic for transient failures. Webhook delivery failures are retried up to five times.

Yes, we provide a sandbox environment for testing integrations before going live. The sandbox mimics all production API endpoints and returns realistic responses without sending actual messages. You can use test WhatsApp numbers and email addresses in the sandbox. This allows you to build, test, and debug your integration risk-free before deploying to production.