Download the PHP package envoisms/envoisms-php without Composer
On this page you can find all versions of the php package envoisms/envoisms-php. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download envoisms/envoisms-php
More information about envoisms/envoisms-php
Files in envoisms/envoisms-php
Package envoisms-php
Short Description Official PHP SDK for EnvoiSMS.ma - direct-operator SMS, WhatsApp Business API (WABA) and OTP/2FA verification for Morocco
License MIT
Homepage https://envoisms.ma
Informations about the package envoisms-php
EnvoiSMS PHP SDK
Official PHP SDK for EnvoiSMS.ma — the direct-operator SMS, WhatsApp Business (WABA) and OTP verification API platform for Morocco (Maroc).
What is EnvoiSMS.ma?
EnvoiSMS.ma routes transactional and marketing messages through direct connections to Morocco's three mobile operators, plus the official WhatsApp Cloud API — no aggregator, no gray SIM routes.
| Channel | What it's for | Covered by this SDK |
|---|---|---|
| SMS Direct Opérateurs — IAM, Inwi, Orange | OTP codes, delivery alerts, marketing SMS, from 0.48 MAD/SMS | ✅ send(), sendBulk() |
| WhatsApp Business API (Meta WABA) | Approved templates, interactive buttons, catalog, multi-agent inbox, from 0.65 MAD/message | ✅ send(['channel' => 'whatsapp']) |
| OTP / 2FA Verification | Send + check one-time codes over SMS or WhatsApp | ✅ sendOtp(), checkOtp() |
| Numéro Virtuel (+212) | Cloud Moroccan business line, no physical SIM, shared team inbox | Manage from the dashboard |
| Assistant IA Conversationnel | Darija/French AI agent for COD order confirmation & support handoff | Manage from the dashboard |
Numéros Virtuels and the AI assistant are configured from your EnvoiSMS.ma dashboard today; dedicated SDK endpoints for them are on the roadmap. Everything below (send, OTP, billing, webhooks) works with the SDK right now.
Quick Start — Send an SMS
Every send() / sendBulk() carries an Idempotency-Key (generated, or pass one as the second argument), so a retry after a timeout can never bill the same message twice.
Choosing a channel: SMS or WhatsApp?
Default to SMS. It reaches every Moroccan mobile (IAM, Inwi, Orange) with no setup beyond your API key, and it is what an "ordinary text to a customer" needs — even when that customer uses WhatsApp.
'channel' => 'whatsapp' is different in kind, not just in name. It sends from your own WhatsApp Business number, which means:
- the number must be connected in your dashboard (WhatsApp tab) — otherwise the API answers
403 WHATSAPP_NOT_CONNECTEDand nothing is charged; - a free-form text is only accepted while the recipient has written to that number in the last 24 hours (
400 OUT_OF_24H_WINDOWotherwise, nothing charged); - outside that window, you send an approved template (
templatefield), not free text.
| You want to… | Use |
|---|---|
| Send a text to a customer (order status, reminder, alert) | 'channel' => 'sms' (the default — just omit channel) |
| Send a one-time code | sendOtp() — pass 'channel' => 'whatsapp' for a WhatsApp code through our shared sender, no connection needed |
| Reply on WhatsApp to a customer who wrote to your number in the last 24 h | 'channel' => 'whatsapp' with message |
| Start a WhatsApp conversation (marketing, utility) | 'channel' => 'whatsapp' with an approved template |
Common mistake: sending an SMS-style text with 'channel' => 'whatsapp' "because the customer is on WhatsApp". Both refusals above name the fix — send it as SMS.
Send a WhatsApp Business Message
Only from a WhatsApp Business number you connected in your dashboard — see the table above. Free text works inside the 24-hour customer window; otherwise send an approved template.
Automatic channel fallback (cascade)
Send over WhatsApp and drop back to SMS automatically when a number is unreachable or has no WhatsApp — the same fallback used for VTC riders on flaky mobile data.
OTP / 2FA Verification
Bulk Sending
Message Status & Delivery
Verifying Delivery Webhooks (DLR)
If you configure a delivery-status webhook, verify its X-EnvoiSMS-Signature header before trusting the payload:
Account & Billing
Analytics & API Keys
Compliance: Opt-outs (STOP)
Error Handling & Retries
The client retries 5xx responses and cURL errors up to maxRetries times (default 2) with exponential backoff, and throws EnvoiSMSError — with statusCode and errorCode properties — on any failure:
Why teams pick EnvoiSMS.ma over an aggregator
- Direct routes to IAM, Inwi and Orange — no international transit hop, no gray-route ban risk.
- 2.4–2.8 second OTP latency, measured across IAM, Inwi and Orange — aggregators routing through Europe typically land in the 10s+ range.
- Billing in MAD, no EUR/USD conversion surprises.
- Local support based in Casablanca, not an offshore ticket queue.
See the full breakdown on envoisms.ma.
Documentation & Pricing
- Full API reference: envoisms.ma/fr/docs
- Pricing & credit packs: envoisms.ma/fr/tarifs
- Real customer use cases: envoisms.ma/fr/cas-usage
- Create a free account (5 MAD credit included): envoisms.ma/fr/register
Other official SDKs
- Python:
pip install envoisms - Node.js / TypeScript:
npm install envoisms - WooCommerce, Shopify, Zapier and Google Sheets integrations: envoisms.ma/fr/integrations
Support
- Email: [email protected]
- Sales: [email protected]
License
MIT
All versions of envoisms-php with dependencies
ext-curl Version *
ext-json Version *