Migrate from Vonage/Nexmo to SendSMS: complete checklist

However, in the face of the increase in routing fees to Morocco (+212) by global aggregators and the need for CNDP compliance, migration to a sovereign API like EnvoiSMS becomes strategic. The transition between two REST API is fast, but requires special attention to data formatting.

The Vonage API and the [EnvoiSMS API] (/fr/api-sms-maroc/) use different naming conventions in their JSON payloads.

Parameter Vonage (Nexmo) Equivalent to SendSMS Data Type:---:---:---:---:--- api_key / api_secret Authorization: Bearer <Token> Header HTTP (Enhanced Security) fromɐs sender_id String (Max 11 alfanumeric characters) to recipient String (Format E.164: +2126XXXXXX)

Note about authentication: Nexmo often accepts the API Key in the URL (GET) or the Body (POST). For reasons of modern security standards, EnvoiSMS requires the token to pass into the HTTP Authorization Header.

On Nexmo, for sending a SMS to France or the UK, you can often invent the field from in your code. In Morocco, the market is regulated (Sender ID Whitelisting).

Before changing your code: You must ask the SendSMS support to validate and officially register your "Sender Name" from Moroccan operators (IAM, inwi, Orange). This validation takes 15 to 30 days: plan it at least 30 days before the switch. If you skip this step, your SMS will generate an error 403 Forbidden or will be blocked by local telecom filters.

If you use Vonage Delivery Receipts (DLR) to update the status of your shipments in your CRM (e.g. mark a OTP code as received), the return format (Callback) will change.

Vonage often sends a status setting (e.g. delivered, failed). With SendSMS, configure the URL of your Webhook in the dashboard. Your server (Endpoint) will receive a standardized JSON payload:```json
{
"message_id": "msg_8f7d6c5b",
"status": "DELIVERED",
"recipient": "+212600000000",
"timestamp": "2026-10-15T14:32:01Z"
}

Do not cut Nexmo from day to day. Apply the Safe Switch Principle: 1. Week 1 (Double Test): Connect SendSMS only to your Staging/Pre-production environments. 2. Week 2 (Transaction Bascle): Spend 100% of your SMS Marketing (Push Promotional) on SendSMS, as they are less critical at second near. 3. Week 3 (OTP Bascle) : If marketing campaigns work perfectly with a good rate of ‘DIVERED’, lower your critical streams (forgotten passwords, server alerts).

By migrating to a local player, you’re not just changing a few lines of JSON code: you move to local routes to the Moroccan operators, with automatic failover between routes, which can reduce delivery latency on Moroccan phones.

Ensuring sub-3-second delivery across Morocco requires direct local carrier connections to Maroc Telecom (IAM), Orange Morocco, and Inwi, paired with automated multi-route failover.

Every payload dispatched to https://api.envoisms.ma/v1/messages is deterministically normalized to E.164 (+212 format). Signed HMAC-SHA256 webhooks stream live Delivery Receipts (DLR: queued, sent, delivered, failed) directly into your backend infrastructure.

All business communications in Morocco are governed by CNDP Law 09-08. Transactional workflows operate under lawful contractual performance (Article 4-b), while promotional dispatches strictly enforce automated STOP opt-out mechanisms (Article 9 & 10).

EnvoiSMS processes data in full adherence to domestic privacy regulations, guaranteeing end-to-end encryption in transit (TLS 1.3) and at rest (AES-256).