# Senden API

> Independent HTTP API for ordinary WhatsApp, Telegram and MAX accounts.

Public site: https://api-senden.ru/
Use cases: https://api-senden.ru/use-cases
Developer guide and complete HTTP catalog: https://api-senden.ru/docs
Security and integration boundaries: https://api-senden.ru/security
OpenAPI: https://api-senden.ru/openapi.json
Machine-readable API context: https://api-senden.ru/downloads/ai-context.json
Integration starter ZIP: https://api-senden.ru/downloads/starter.zip
Full text: https://api-senden.ru/llms-full.txt

API base: https://api-senden.ru/api/v1
Named Bearer key required for private operations. Register at https://api-senden.ru/register and sign in at https://api-senden.ru/login.
GET /api/v1/integrations/manifest returns only the authenticated workspace's safe instances, connectedMessengers, permissions and the complete commands catalog. GET /methods is only a native-operation subset.
Never request a password, QR, verification code, API key or session token in a public prompt. Keep keys in server-side secrets.
Do not send messages, start messenger login, upload files, lease notifications or mutate settings automatically. Obtain explicit authorization for mutations.
Select real chat IDs from GET /api/v1/instances/{id}/chats. For MAX, contacts.lookup currently exposes a user ID under chatId; do not treat it as a private-chat destination.
Use one stable Idempotency-Key for each send or native mutation. 202/queued/submitted is not proof of delivery. Unknown outcomes must not be replayed with a new key.
Capabilities differ by messenger and account state. No official messenger partnership, uptime SLA, AI model, CRM-specific module or guarantee against account restrictions is claimed.