An order ready to collect.
Your system triggers an update when an order changes state.
Illustrative messageYour order is ready for collection.
SMS API · Morocco
SMS inside
your application.
Send your application-generated OTPs, alerts and notifications to Moroccan recipients. An HTTPS API, individual message tracking and signed webhooks.
Included in Essentiel and Croissance. API sending uses your account allowance and requires an active plan.
curl 'https://smsmarocpro.com/v1/messages' \
--header 'Authorization: Bearer <YOUR_SERVER_KEY>' \
--header 'Content-Type: application/json' \
--header 'Idempotency-Key: order_2026_000001_ready' \
--data '{
"to": "+2126XXXXXXXX",
"trafficClass": "transactional",
"text": "Your order is ready."
}'202 Accepted
Request accepted. Keep its identifier to track the outcome.
Illustrative example only: this page sends no SMS. Replace masked values in your own server integration.
From your event to the outcome
One request.
A clear status.
Each message keeps its identifier. An HTTP response and receipt on the recipient's phone are different events.
- 01 YOUR APPLICATION
Trigger
Create a business operation and persist its idempotency key before the request.
Idempotency-Key - 02 SMSMAROCPRO API
Accept and track
HTTP 202 confirms admission. A valid replay of the same request returns the same message.
GET /v1/messages/{id} - 03 YOUR ENDPOINT
Receive the outcome
Verify the signature and deduplicate events. Confirmed receipt remains distinct from transmission.
message.sent / message.delivered
Inside your product
Turn your events into useful updates.
Your application chooses the recipient, content and timing. SMSMarocPro provides SMS transport and status tracking.
A reminder at the right time.
Your application calculates when to send and handles changes and cancellations.
Illustrative messageReminder: your appointment is tomorrow at 10 am.
The code comes from your application.
You generate, expire and verify your codes. SMSMarocPro transports their SMS messages.
Illustrative messageYour verification code: [code generated by your application].
A controlled integration
Good practices,
from your first request.
Protect credentials and keep retries understandable when your application encounters an unexpected result.
Read the retry guide →Keep keys on your server
Create a key with the required permissions. Keep secrets out of browsers, URLs and logs.
Replay the same request
After an uncertain response, reuse the original key and content. A new key represents a new request.
Verify your webhooks
Check the signature against the raw body, store the event durably and respond promptly. The guide covers retries and secret rotation.
Check your limits
Check availability, allowance and daily maximum. HTTP 202 does not promise immediate transmission or receipt.
For your developer
The reference,
when you need more.
The public contract, examples and integration rules are available without an account. Choose the reference that fits your next step.
Prepare your integration
Your next request starts here.
Create an account to explore credentials and choose your plan. API sending uses the resources of your active subscription.