Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.modawer.com/llms.txt

Use this file to discover all available pages before exploring further.

​
Overview

Use these endpoints to queue OTP messages and raw WhatsApp payloads for delivery.
These endpoints queue messages for async processing. A successful 200 OK response means the request was accepted for processing, not that the message has already been delivered.

​
Available endpoints

Send OTP message

Send one OTP through Modawer’s official WhatsApp account.

Send raw message

Queue a raw WhatsApp template payload.

​
Shared behavior

  • Authentication is handled with the X-API-KEY header.
  • Route-level JWT authentication is not required.
  • When a dev token is used, messages are routed to the app’s linked Telegram chats instead of the provided recipient.
  • Send OTP Message uses Modawer’s official WhatsApp account and is the fastest way to start sending OTPs.
  • To send from a custom sender ID, link your WABA account in the Modawer Portal.
  • OTP templates require a verified WhatsApp Business Account (WABA) when using your own sender.
  • Utility and marketing templates can be sent from a linked WhatsApp account without completing business verification.

​
Request conventions

  • JSON property names are camelCase.
  • OTP messages use the built-in otp_code_1 authentication template.
  • Raw messages wrap the WhatsApp payload in a top-level payload object.

​
Next pages

Link WABA account

Connect your WhatsApp Business Account and custom sender.

Number migration

Move an existing WhatsApp API number to Modawer.

Authentication

Learn how app tokens and dev tokens behave.