SMS API

Send OTP codes and notifications straight from your system

One HTTPS GET request from your backend. Use the SMS API to send OTP codes and transactional notifications from your own backend, inside Egypt.

Available inside Egypt only

HTTPS GET

What you can build

Messages your system sends at exactly the right moment

  • OTP verification codes

    A login or confirmation code that reaches the customer seconds after they ask for it.

  • Order confirmations

    An automatic message when an order completes or changes state in your store.

  • Shipment updates

    A notice when a shipment leaves, or when the courier is close.

  • Internal system alerts

    An appointment reminder, a renewal alert or an invoice notice, straight from your system.

Who this is for

  • Developers and software companies
  • E-commerce stores
  • Mobile applications
  • Internal business systems
  • Shipping and delivery companies
  • OTP verification codes
  • Banking and ATM transaction alerts
  • Loyalty and rewards program notifications
  • Web transaction confirmations

In every case the API sends alerts and notifications requested by the customer’s own software. It does not carry out any transaction and does not connect to ATM hardware.

How it works

Four steps from event to message

  1. An event happens in your system

    A signup, an order confirmation, a shipment leaving.

  2. Your server builds the request

    It assembles the numbers, message and language, URL-encoding every value.

  3. An HTTPS GET goes to the gateway

    From the backend only — never the browser, never the app.

  4. The gateway replies in plain text

    You match the response strictly before treating it as success.

The integration

One request from your server

https://sms.masrbokra.com/sendsms.php

Protocol
HTTPS
Method
GET
Request format
URL-encoded query parameters
Response
Plain text, not JSON
Encoding
UTF-8

Required send parameters

Field Type Description
user String API account username
password String API account password
numbers String One international number, or a comma-separated list
sender String The sender name approved on the account
message String The message text, UTF-8
lang Enum Message language: en or ar

Request acknowledgement

  • 1
  • 1:<valid-recipient-list>

The gateway replies in plain text: 1 when the request is accepted, or 1 followed by the accepted recipient list. The full response tables are in the integration guide.

Balance query

The same endpoint with user, password and action=get. The gateway returns a numeric value as plain text, which may include decimals.

Implementation note: Keep your API credentials on the server. The call is made from your backend — not from the browser, and not from inside a mobile app.

Code examples

Server-side integration examples

Your account credentials are supplied separately through a secure channel after activation.

# Credentials come from the environment, never from the command line
# (a literal password would land in your shell history).
curl --get "https://sms.masrbokra.com/sendsms.php" \
  --data-urlencode "user=$MASRBOKRA_SMS_USER" \
  --data-urlencode "password=$MASRBOKRA_SMS_PASSWORD" \
  --data-urlencode "numbers=201001234567" \
  --data-urlencode "sender=YOUR_SENDER" \
  --data-urlencode "message=Your order has shipped." \
  --data-urlencode "lang=en" \
  --connect-timeout 10 \
  --max-time 20 \
  --no-retry-all-errors

# The reply is plain text: "1", or "1:201001234567", or an error string.

Number format

International digits only — no plus sign, no spaces, no dashes. Supported Egyptian prefixes: 010, 011, 012, 015.

Local input Value sent
01001234567 201001234567
01112345678 201112345678
01212345678 201212345678
01512345678 201512345678

SMS packages

The larger the package, the lower the per-message price

The same packages cover Bulk SMS and the API. It is one balance on your account.

SMS units Price Per message
1,000 270 EGP 0.270 EGP
5,000 1,350 EGP 0.270 EGP
10,000 2,650 EGP 0.265 EGP
20,000 5,200 EGP 0.260 EGP
50,000 12,750 EGP 0.255 EGP
100,000 25,000 EGP 0.250 EGP
150,000 Lowest unit price 36,750 EGP 0.245 EGP

All prices exclude VAT at 14%.

Request your package

Sender Name activation

Your company’s name on the message, not an unknown number

One sender-name activation serves both Bulk SMS and the API.

Activation fee
2,150 EGP
Activation time
7–10 business days
Documents required
  • Commercial Register
  • Tax Card

The activation fee excludes VAT. Terms and conditions apply.

Talk to the technical team

Start your integration with our team

Our technical team helps you set the account up, walks through the testing steps and follows up on any sending issue once you are live.

  • Lightweight HTTPS GET integration
  • Plain-text response handling
  • Direct SMS sending and balance lookup
  • Account credentials supplied separately and securely
Request the SMS API Integration Guide

Common questions

Questions about the SMS API

What do I need to get started?

An API account, an activated Sender Name and an SMS balance. We set the account up and send your technical team the credentials and the integration guide.

Which programming languages are supported?

Any language that can make an HTTPS request. The guide includes ready examples in cURL, PHP, Node.js and Python.

Is the balance shared with Bulk SMS?

Yes. The same packages and the same balance cover the platform and the API, and you can use both in parallel on one account.

Can I schedule sends?

Scheduling is available in the Bulk SMS platform. With the API, your own system schedules on its side and calls the endpoint at the moment you choose.

Start the integration

Tell us about your system and your expected volume; we will set up the account and sender name and send your team the full guide.