Skip to main content
POST

Important Notes

Phone Format: Always use E.164 format for phone numbers (e.g.: +PHONE_NUMBER) to ensure compatibility across different regions.
Contact Completeness: Although all fields are optional, providing complete contact information (name, phone, email) improves the user experience and makes contacts more useful.

Use Cases

  • Sharing support contact information
  • Referring users to specific team members
  • Providing business card information
  • Sharing emergency contacts

Authorizations

Authorization
string
header
required

Basic authentication using Base64 encoded clientId:clientSecret

Path Parameters

botId
string
required

The unique identifier of the bot

Body

application/json

Message payload. The structure varies based on the message type.

type
enum<string>
required

Type of message to send

Available options:
text
Example:

"text"

userId
string
required

Unique identifier of the user receiving the message. Accepts either a phone number in E.164 format without the leading '+' (e.g. '593999999999') or a BSUID (Business-Scoped User ID, e.g. 'US.13491208655302741918') for users who have enabled phone number privacy in WhatsApp.

Example:

"593999999999"

text
string
required

Text content of the message

Example:

"Hello, this is a text message"

botId
string

Unique identifier of the bot sending the message

Example:

"BOT_ID"

Response

Message sent successfully

success
boolean
Example:

true

messageId
string
Example:

"msg_123456789"