Start with one request.

1. Create an account and a connection

Register with your email, verify the address using the email message and sign in to the dashboard. Choose a messenger and complete its available QR or phone-number sign-in flow. Telegram requires your own application API credentials. Any additional sign-in steps are shown in the dashboard.

2. Create an API key

In Profile → API keys, create a separate key for your project. Reading is allowed by default; the write permission is required for sending and other changes. The value is shown only once. Store it in backend secrets, not in the browser, Git or an AI prompt.

3. Retrieve connections and the full catalog

curl 'https://api-senden.ru/api/v1/integrations/manifest' \
  --header 'Authorization: Bearer YOUR_API_KEY'

The response contains instances, connectedMessengers, commands and permissions. Подключения относятся только к вашему пространству, архивные исключены явно. Для отправки выберите аккаунт со state: connected.

4. Choose a chat, send and check the result

Get actual chat IDs using GET /api/v1/instances/{id}/chats. Send text and files using POST /api/v1/instances/{id}/messages with one stable Idempotency-Key. A 202 response means queued, not delivered. Status and incoming messages are available through history, SSE, webhooks and the notification queue. See transport capabilities below.

For MAX, contacts.lookup currently returns a user ID that must not automatically be treated as a private chat ID. Use an ID from the chat list as the destination. Do not resend a message with a new key while the outcome of the first send is unknown.

Events and webhook security

For webhooks, verify the HMAC signature and process events idempotently. The endpoint must be a public HTTPS address; local and private networks are blocked. SSE provides an event stream; receiving a notification from the queue creates a lease and requires write, followed by an ack. Full parameters and request formats are provided in OpenAPI.