Non-Template Message

Send instant WhatsApp messages directly to your customers without requiring pre-approved templates. Perfect for quick responses, customer support, and media sharing during ongoing conversations.

The Send Non-Template Message API enables you to send immediate WhatsApp messages including text, images, videos, audio, and documents. This is ideal for customer support scenarios and ongoing conversations where template approval is not required.

Overview

The Send Non-Template Message API enables you to:

Send instant text messages with URL previews
Share images, videos, and documents with captions
Send audio files and voice messages
Organize messages with custom labels for analytics
Respond quickly in customer support scenarios
Continue conversations without template restrictions

Send Non-Template Message

Send various types of WhatsApp messages directly to a specific phone number without requiring pre-approved templates.

Endpoint

POST https://api.insightssystem.com/api:U9ztporN/send/message

Authentication

All API requests require authentication using your API key. Never share your API keys in client-side code or public repositories.

Include your API key in all requests using Bearer authentication:

Authorization: Bearer YOUR_API_KEY

Request Body

string

required

The recipient’s phone number in international format with country code (e.g., “+15551234567”).

type

string

required

The type of message to send. Must be one of: text, image, video, audio, document.

api_key

string

required

Your API key for authentication (also required in request body).

recipient_type

string

default:"individual"

The type of recipient. Always use “individual” for single recipients.

messaging_product

string

default:"whatsapp"

The messaging platform. Always use “whatsapp”.

labels

array

Array of strings for message categorization and analytics (e.g., [“support”, “urgent”]).

Message Type-Specific Parameters

text

object

required

Text message configuration

Show Text Properties

body

string

required

The text content of the message (max 4096 characters)

preview_url

boolean

default:"false"

Whether to show URL previews for links in the message

Response

The API returns a detailed response indicating whether the message was accepted for delivery and provides WhatsApp message identifiers for tracking.

success

boolean

Indicates if the request was successfully processed

whatsapp_response_info

object

Details from the WhatsApp Business API about the message delivery

Show WhatsApp Response Fields

messaging_product

string

Always “whatsapp” for WhatsApp messages

contacts

array

Information about the message recipient

input

string

The phone number that was provided in the request

wa_id

string

WhatsApp’s unique identifier for the recipient

messages

array

Details about the sent message

string

Unique message identifier (wamid) for tracking status

message_status

string

Initial status of the message (typically “accepted”)

error

object

Present only when an error occurs

code

string

Error code identifier

message

string

Human-readable error description

Example Requests

curl -X POST \
  https://api.insightssystem.com/api:U9ztporN/send/message \
  -H 'Content-Type: application/json' \
  -H 'Authorization: Bearer YOUR_API_KEY' \
  -d '{
    "to": "+15551234567",
    "type": "text",
    "text": {
      "body": "Hello! Thank you for contacting our support team. How can we help you today?",
      "preview_url": true
    },
    "api_key": "YOUR_API_KEY",
    "recipient_type": "individual",
    "messaging_product": "whatsapp",
    "labels": ["support", "greeting"]
  }'

Example Response

{
  "success": true,
  "whatsapp_response_info": {
    "messaging_product": "whatsapp",
    "contacts": [
      {
        "input": "+15551234567",
        "wa_id": "15551234567"
      }
    ],
    "messages": [
      {
        "id": "wamid.HBgLMTU1NTEyMzQ1NjcVAgAERgINQTlEOEJDNzM5QzQwAA==",
        "message_status": "accepted"
      }
    ]
  }
}

Response Codes

200: Success

400: Bad Request

The request was invalid. Check the error message for details about missing or invalid parameters.

{
  "success": false,
  "error": {
    "code": "missing_required_field",
    "message": "The 'to' field is required and must be a valid phone number"
  }
}

401: Unauthorized

Authentication failed. Verify that you’re using a valid API key in both the header and request body.

{
  "success": false,
  "error": {
    "code": "unauthorized",
    "message": "Invalid API key provided"
  }
}

403: Forbidden

413: Payload Too Large

422: Unprocessable Entity

The request contains invalid data or the media URL is not accessible.

{
  "success": false,
  "error": {
    "code": "invalid_media_url",
    "message": "The provided media URL is not accessible"
  }
}

429: Too Many Requests

500: Server Error

An internal server error occurred. Contact support if the issue persists.

{
  "success": false,
  "error": {
    "code": "server_error",
    "message": "An internal server error occurred. Please try again later."
  }
}

Message Types Guide

Understanding the different message types and their optimal use cases will help you choose the right format for your communication needs.

Text Messages

Best Practices

Keep messages concise and actionable
Use URL previews for important links
Break long messages into multiple shorter ones
Include clear call-to-action when needed

Use Cases

Customer support responses
Order confirmations
Quick updates and notifications
FAQ responses

Media Messages

Images

Formats: JPG, JPEG, PNG
Max Size: 5MB
Optimal: 1080x1080px or 16:9 ratio
Use for: Product photos, screenshots, infographics

Videos

Formats: MP4, 3GPP
Max Size: 16MB
Max Duration: 90 seconds
Use for: Tutorials, product demos, explanations

Audio

Formats: MP3, AAC, AMR, OGG
Max Size: 16MB
Max Duration: 30 minutes
Use for: Voice messages, audio instructions

Documents

Formats: PDF, DOC, DOCX, PPT, PPTX, XLS, XLSX
Max Size: 100MB
Use for: Manuals, invoices, reports, contracts

Media Requirements

All media URLs must be publicly accessible via HTTPS without requiring authentication. For security-sensitive content, consider using signed URLs with expiration times.

URL Requirements

Public Accessibility

Ensure your media URLs are publicly accessible without authentication headers or login requirements.

HTTPS Protocol

All media URLs must use HTTPS protocol. HTTP URLs will be rejected.

Direct File Access

URLs should point directly to the file, not to a page that contains the file or requires redirects.

Content-Type Headers

Your server should return appropriate Content-Type headers for media files to ensure proper handling.

Supported Formats

Media Type	Supported Formats	Max Size	Notes
Images	JPG, JPEG, PNG	5MB	Animated GIFs not supported
Videos	MP4, 3GPP	16MB	H.264 codec recommended
Audio	MP3, AAC, AMR, OGG	16MB	Stereo or mono
Documents	PDF, DOC, DOCX, PPT, PPTX, XLS, XLSX	100MB	Password-protected files not supported

Best Practices

Message Optimization

Keep messages concise and actionable. Use rich media when it adds value. Always include clear next steps or calls-to-action when appropriate.

Error Handling

Implement comprehensive error handling with retries. Store failed messages for later retry. Monitor success rates and investigate patterns in failures.

Media Management

Use CDN for media hosting to ensure fast loading. Implement media validation before sending. Consider file size optimization for better delivery rates.

Analytics & Tracking

Use labels consistently for message categorization. Track message IDs for delivery status monitoring. Implement webhook handling for real-time status updates.

Security Considerations

API Key Security

Never expose API keys in client-side code
Use environment variables for key storage
Rotate keys regularly
Implement IP whitelisting when possible

Data Privacy

Avoid sending sensitive data in message content
Use secure, time-limited URLs for confidential documents
Implement proper access controls
Follow GDPR and other privacy regulations

FAQs

Can I send messages to users who haven't messaged me first?

Why are my media messages failing?

How do I track message delivery status?

Can I schedule messages for later delivery?

What happens if the recipient doesn't have WhatsApp?

How do I handle different time zones for my recipients?

Need help?

Our support team is available 24/7 to help with API integration, troubleshooting, or any questions about sending messages.

Get Started

WhatsAble

Notifier by WhatsAble

Notifyer System

Overview

Send Non-Template Message

Endpoint

Authentication

Request Body

Message Type-Specific Parameters

Response

Example Requests

Example Response

Response Codes

Message Types Guide

Text Messages

Best Practices

Use Cases

Media Messages

Images

Videos

Audio

Documents

Media Requirements

URL Requirements

Supported Formats

Best Practices

Message Optimization

Error Handling

Media Management

Analytics & Tracking

Security Considerations

API Key Security

Data Privacy

FAQs

Need help?

Get Started

WhatsAble

Notifier by WhatsAble

Notifyer System

​Overview

​Send Non-Template Message

​Endpoint

​Authentication

​Request Body

​Message Type-Specific Parameters

​Response

​Example Requests

​Example Response

​Response Codes

​Message Types Guide

​Text Messages

Best Practices

Use Cases

​Media Messages

Images

Videos

Audio

Documents

​Media Requirements

​URL Requirements

​Supported Formats

​Best Practices

Message Optimization

Error Handling

Media Management

Analytics & Tracking

​Security Considerations

API Key Security

Data Privacy

​FAQs

Need help?

Overview

Send Non-Template Message

Endpoint

Authentication

Request Body

Message Type-Specific Parameters

Response

Example Requests

Example Response

Response Codes

Message Types Guide

Text Messages

Media Messages

Media Requirements

URL Requirements

Supported Formats

Best Practices

Security Considerations

FAQs