Today, it's not only the speed of communication with customers that matters for business, but also the ability to automate processes. Using APIs, companies can centralize communication, reduce the load on operators, and increase conversion. The WAMM.chat service offers a unified API for connecting the messengers WhatsApp, Telegram Personal, Telegram Bot, MAX Personal, which opens up broad integration possibilities with CRM systems, websites, and corporate systems.

Our API for integrating messengers into a SaaS product is specifically designed to allow developers to quickly implement communication features into their platforms. A key advantage is the ability to organize direct sending and receiving of messages from a personal account (MAX, WhatsApp, or Telegram Personal). This allows businesses to maintain a "human touch" in correspondence, avoiding the strict limitations of official bots and increasing customer loyalty through a familiar communication format.

The Messenger API from WAMM.chat is a single unified interface that allows working with multiple channels simultaneously: WhatsApp, Telegram, and MAX. Through the API, you can: send and receive messages, delivery and read statuses; manage contacts and chats; attach files and images; and much more. For example: an online store can use the API to send an order confirmation via WhatsApp, a delivery reminder via Telegram, and a promotional mailing via MAX. All within one system.

For each communication channel supporting the API, you can create an API Token in the Settings > Management > API section, which is used to send requests. You can also specify a public URL for your system - a Webhook URL, which will receive and process messages from messengers without additional API requests. All incoming messages will be sent to your server in real-time.


Messenger API

The API is available for the following messengers: WhatsApp, MAX Personal, Telegram Personal, Telegram Bot.

This documentation is an accessible reference containing all the necessary tools for working with all messengers through a single interface. This detailed guide will help you quickly set up automation methods: from simple text sending to managing complex dialogue chains, ensuring stable communication between your service and the outside world.


Request Addressing

All API requests should be directed to the base URL:

https://wamm.chat/api2/

Request results and messages to the WebHook URL are returned in JSON format.

{"err":0,"msg_id":1xxxxx}

Authentication

To work with the API, a token is used—a unique key passed in the request.

Example URL with a token:

https://wamm.chat/api2/msg_to/YOUR_TOKEN/?phone=79001234567&text=Message text

If the token is invalid or missing, the API will return an error:

{"err":"token fail"}

If the channel is not authorized or not ready to send messages, the API will return an error:

{"err":"acc not authorized"}

Otherwise, if the token is valid and the channel is authorized, the request will return the requested data.

{"err":0, "msg_data":"..."}

Capabilities, Available API Methods


If you need additional API methods and data for more comprehensive integration - write to our Support and we will add them!



API documentation is also available on the ReadMe.io portal (https://wammchat.readme.io)


Important: The API is served by a group of servers with IP addresses: 91.240.84.65, 188.127.243.197, 31.135.9.55, 82.146.53.215, 45.130.42.197. You can configure filtering by these IP addresses for additional security.