Getting started
Find your API login and password in the account dashboard. Access requires verified email, an active subscription or trial, and a configured downstream connection. The API password is displayed once.
Example request
curl -X POST 'https://api.sendsend.dev/v1/commands' \
-u 'YOUR_API_LOGIN:YOUR_API_PASSWORD' \
-H 'Content-Type: application/json' \
-H 'Idempotency-Key: order-4522-notify' \
-d '{"channel":"telegram","recipient":"RECIPIENT_ID","message":"Your order is ready"}'The JSON object accepts `channel` (telegram, viber or whatsapp), `recipient` in your connector's accepted format and `message` text.
Authentication and limits
- HTTPS and HTTP Basic. Keep API credentials on your server, not in browser JavaScript.
- Use a unique `Idempotency-Key` (8–128 characters) for safe retries.
- There are per-IP and per-account rate limits.
- Default maximum request body size is 64 KB.
Response codes
- `202`: accepted by downstream, not proof of delivery.
- `401`: invalid credentials.
- `402`: subscription required.
- `409`: idempotency conflict or request still processing.
- `422`: invalid payload.
- `429`: rate-limited.
- `502` / `503`: connection unavailable.
{"ok":true,"request_id":"...","status":"accepted"}Security
Internal destination URLs are never exposed in API responses. API logs hold request metadata, not message text or recipient identifiers. Obtain recipient consent before messaging.