Using the API

Overview

The Wallm API is a RESTful API that allows you to send and receive WhatsApp messages programmatically. All API requests are authenticated using your API key.

Base URL

All API requests should be made to:

https://api.wallm.com/v1

Authentication

Every request must include your API key in the request headers. Use the X-Api-Key header:

X-Api-Key: wlm_live_a1b2c3d4e5f6g7h8i9j0k1l2m3n4o5p6

Example Request

Here's an example of sending a text message:

POST /v1/sessions/{session_id}/messages/text
Content-Type: application/json
X-Api-Key: wlm_live_a1b2c3d4e5f6g7h8i9j0k1l2m3n4o5p6

{
  "to": "+966501234567",
  "text": "أهلا, عساك بخير؟"
}

API Documentation

For the complete API reference, including all available endpoints, request/response schemas, and interactive examples, visit our API Documentation.

Rate Limiting

To ensure fair usage and prevent abuse, the Wallm API implements rate limiting. Rate limits are applied per account based on your subscription plan.

Rate limit headers:

X-RateLimit-Limit: 100
X-RateLimit-Remaining: 95
X-RateLimit-Reset: 1716123456

If you exceed the rate limit, you'll receive a 429 Too Many Requests response. Wait until the reset time before making additional requests.

Botting Protection

Wallm implements automated botting protection to prevent misuse of the platform. This includes:

• Spam detection — messages sent too rapidly or in high volumes may be flagged
• Unusual activity monitoring — sudden spikes in message volume trigger protective measures
• Temporary blocks — excessive requests may result in temporary API access restrictions

To avoid triggering botting protection:

• Implement proper rate limiting in your application
• Space out message sending rather than batch-sending thousands at once
• Use the API responsibly and as intended

Important API Practices

• Always check if a WhatsApp number exists before sending messages. Sending messages to non-existent numbers may result in temporary blocks
• Use webhooks to receive inbound messages rather than polling
• Monitor your credit usage to avoid unexpected overages
• Handle errors gracefully — implement proper error handling for 4xx and 5xx responses