MESSENGERS + YOUR SYSTEM

Your messages.
At the pace of your business.

Connect WhatsApp, Telegram and MAX to your CRM, website or application through one API.

Personal accounts. Your own workspace. From the first message to events in your system.

Create workspace Explore the API

Already using Senden? Open dashboard ↗

One integration point ILLUSTRATION
WorkspaceYOUR DASHBOARD

Accounts and integrations

WhatsAppQR or pairing code
Account
T
TelegramQR or phone number
Account
M
MAXPersonal account connection
Account
QueueAPI keysEvents
Your CRMSenden APIMessenger

Illustration of the service. Create real connections in the dashboard.

70HTTP commands
in the published API
35native commands
in the catalog
Node.js + Pythonclient examples
for your integration
OpenAPI + Postmanschema and collection
of requests

Native commands vary by messenger. Check the catalog for support.

MORE THAN SENDING TEXT

Less manual work.
More connections between systems.

Make each message part of a lead, order or conversation. You define the logic; Senden provides the API and events.

Explore use cases

Your CRM or application controls triggers, scheduling and business rules.

01CRM and salesLEADS

Notify about new leads, continue conversations and send message events back to the customer record.

Lead in CRMMessage to customerEvent in CRM
02Online storeORDERS

Link messages to order updates: confirmation, packing and collection. Send documents and explanatory text.

New statusMessage and file
03Customer supportCONVERSATIONS

Send incoming events to your support system and reply through the same connected account.

Incoming messageYour support teamReply
04Bookings and appointmentsSERVICE

Let your system send booking confirmations, appointment reminders or schedule changes.

Calendar eventNotification
05Logistics and deliverySTATUS UPDATES

Send cargo readiness, collection times and delivery updates from your business system.

Delivery updateMessage to recipient
06Your AI assistantAUTOMATION

Connect your assistant to messengers through the API and webhooks. You choose the model, response rules and human handoff.

EventYour assistantReply via API

FROM REQUEST TO RETURN EVENT

One interface.
The complete message journey.

Build integrations with clear HTTP requests. Monitor the queue and handle results in your system.

Queue and idempotency

Send requests are saved in the queue. Idempotency-Key helps prevent duplicate actions when the same request is retried.

Text, files and history

Send messages and documents. View logs and processing status in the dashboard or through the API.

Webhooks, SSE and events

Receive events in a handler, read the SSE stream or use a notification queue with processing acknowledgements.

First request · Bash / cURL
GET/api/v1/integrations/manifest
curl 'https://api-senden.ru/api/v1/integrations/manifest' \
  --header 'Authorization: Bearer YOUR_API_KEY'

Connections, commands and integration materials for your workspace. This request only reads data.

Documentation and command catalog
YOUR WORKSPACE

Everything you need to manage integrations.

  • Registration with email verification
  • Isolated data and personal API keys
  • User dashboard and administration
  • Connections, queue, history and guides

START WITH ONE USE CASE

Four steps.
Your own integration.

Download starter kit
  1. 01

    Create a workspace

    Register and verify your email to access your dashboard.

  2. 02

    Connect an account

    Choose a messenger and sign in with QR or phone.

  3. 03

    Create an API key

    Create a key in your Profile and assign read or write permissions.

  4. 04

    Connect your systems

    Use the REST API, client examples and events for your workflow.

For developers and AI assistantsOpenAPI ↗llms.txt ↗Full context ↗Guides ↗

KNOW BEFORE YOUR FIRST REQUEST

What to know
before you start.

Personal accounts remain subject to messenger rules and limits. Test your intended workflow on your own account before production use.

Active development

The service is evolving. Check the current API catalog for features and command support.

Bots or personal accounts?

The service connects personal WhatsApp, Telegram and MAX accounts. Sign-in uses QR, phone or pairing code depending on the messenger. Confirmation uses the messenger’s own authentication.

Do all three messengers support the same commands?

No. Shared HTTP routes and native capabilities differ. The catalog lists supported messengers per command; the dashboard shows connection status.

Does an accepted request mean the message was delivered?

No. A message may only be queued or handed to the messenger. Handle confirmed statuses and errors separately. Delivery also depends on the messenger and recipient.

Can account restrictions be ruled out?

No. Messengers apply their own account rules and limits. Senden API cannot guarantee freedom from restrictions and is not intended for spam or messages without recipient consent.

What if an HTTP request is repeated?

For supported actions, reuse one Idempotency-Key for one logical request. Use a new key for a new action. Check the result and status before retrying a send with an uncertain outcome.

Is there a ready-made integration for every CRM or AI bot?

Senden provides the API, events, documentation and Node.js/Python examples. CRM connectivity, AI assistant logic and business rules are implemented in your system. A working use case depends on that integration.

How is data access managed?

Connections and data belong to an isolated workspace. Create personal API keys with read or write permissions for integrations. Do not share keys in URLs, messages or with AI assistants.

CONNECT WHAT ALREADY WORKS

Your system.
Your accounts.
One Senden API.

Start with one account and one useful workflow. Add more as your integration grows.

Create workspace