SMS overview
Add SMS to your application
Section titled “Add SMS to your application”SMS v2 lets you send a message to a Madagascar mobile number, schedule a message or batch, and retrieve the outcome. The contract uses JSON and English responses. Guides and descriptions are available in French and English.
Product base: https://api.befiana.cloud/api/sms/v2/.
Authentication uses an organization bf_sms_ key in Authorization: Bearer <key>. The key determines the organization. This authentication contract applies to SMS v2; it does not define authentication for other BEFIANA products.
Choose an operation
Section titled “Choose an operation”Scroll horizontally if needed. Keyboard: Tab, then the left and right arrow keys.
| Need | Operation | Guide |
|---|---|---|
| Send now | POST /messages/ without send_at | Immediate sending |
| Schedule a message | POST /messages/ with send_at | Scheduling |
| Schedule multiple recipients | POST /message-batches/ | Batches |
| Retrieve an outcome | GET /messages/{message_id}/ | Statuses |
| Read credits or manage a contact | GET /balance/, POST /contacts/ | Credits and contacts |
Every path in the table is relative to the product base.
Rules to know
Section titled “Rules to know”- A message contains at most two SMS segments.
- An idempotency key is required when creating a message or batch.
- Scheduled messages reserve their credits at admission.
- HTTP
201or202acceptance does not prove delivery. - Sender names are managed in Cloud.
- The available tracking workflow uses API lookups. Customer webhooks and a dedicated OTP endpoint are not part of this contract.
Start with your first SMS, then follow the integration workflow. Exact constraints remain in the reference.
Already using v1?
Section titled “Already using v1?”Historical routes remain under /api/smsko/v1/. Read the migration guide to adapt authentication, fields and tracking. V2 rejects a historical key even if it has been associated with an organization.