Documentation Index
Fetch the complete documentation index at: /llms.txt
Use this file to discover all available pages before exploring further.
Status codes and what to do about them.
errors array instead of
data.
{
"status": "400 BAD REQUEST",
"code": 400,
"message": "Validation failed",
"timestamp": "2026-08-22T12:00:00Z",
"reqId": "REQ4C1B90AE",
"path": "/api/v3/outgoings/send",
"errors": ["senderId is required"]
}
| Code | Meaning | What to do |
|---|---|---|
400 | Validation failed | Read errors. Usually a missing field or a malformed number. |
401 | Not authenticated | Token missing, malformed, or expired. Obtain a new one. |
403 | Not permitted | Your account lacks permission for this endpoint. |
402 | Insufficient credits | Top up. Nothing was sent. |
404 | Not found | Check the path and any ID in it. |
429 | Too many requests | Back off and retry more slowly. |
500 | Server error | Safe to retry after a short delay. If it persists, contact support with the reqId. |
202 sends the messages again and charges again.Only retry when you did not receive a response at all, or on 500. Never retry a
202, a 400, or a 402.reqId from the failing response when you contact
contact@hudumasms.com — it identifies the exact
request in the logs.