Send SMS to Palestine
from $0.0310/msg

smsroute.cc delivers SMS to Palestine's 6 million mobile subscribers via Jawwal (52% market share) and Ooredoo (48% market share) at $0.0310 per message — 57% cheaper than Twilio. Median latency is 175 ms; delivery success rate is 94.8%. No KYC at signup. Pay with Bitcoin, USDT (TRC-20), Ethereum, Litecoin, Monero, or Solana. Requires PTA sender-ID pre-approval (West Bank, 4–5 business days) or de facto Jawwal approval (Gaza). 99.9% uptime SLA.

Why Arabic SMS Segments Cut Your Palestine Character Budget in Half

Palestinian mobile carriers route all SMS traffic according to the encoding rules published by ETSI (European Telecommunications Standards Institute) and enforced by the PTA. When you send SMS containing Arabic script — the primary language in Palestine — the message is automatically converted to UCS-2 encoding by your carrier's SMS gateway. UCS-2 supports the full Unicode character set, including Arabic diacritics, but carries a severe character penalty.

In GSM-7 encoding (used for English, numbers, and basic Latin punctuation), you can fit 160 characters in a single SMS segment. In UCS-2 encoding, that limit drops to 70 characters per segment. If you send an Arabic message of 150 characters, it will be billed as two segments instead of one. A 500-character Arabic announcement costs 7–8 segments; the same announcement in English costs 4 segments. Budget 2–3× more segment volume when targeting Palestinian subscribers with Arabic content.

Example: A promotional message "أهلا وسهلا بك في مخزننا الجديد" (28 characters in Arabic) fits in a single GSM-7 segment if transliterated to Latin, but triggers UCS-2 encoding and counts as 1 segment. A longer campaign message of 145 Arabic characters requires 3 segments; the same text in English requires only 1 segment. This encoding overhead directly impacts your SMS budget for Palestine-focused campaigns.

smsroute.cc's billing engine automatically detects the script and encoding type of each message, calculates the segment count correctly, and charges you only for actual segments sent — not a flat rate per message. You will not be overcharged for multi-segment Arabic SMS.

GSM-7 vs. UCS-2 Encoding and Operator Reach

Palestinian carriers (Jawwal and Ooredoo) enforce encoding rules at the SMSC (Short Message Service Center) level. When your message is submitted to the gateway, the SMSC examines the character set:

• GSM-7 (7-bit encoding): Supports English, numbers, space, and basic punctuation (@, !, ?, -, etc.). Maximum 160 characters per segment. Latin text, transaction IDs, and numeric PINs route efficiently on GSM-7.
• UCS-2 (16-bit Unicode): Required for Arabic, Hebrew, Farsi, Urdu, and any mixed-script content. Maximum 70 characters per segment. All Arabic SMS, irrespective of diacritic use, trigger UCS-2 encoding.

Jawwal (Palestinian Cellular Communications), the largest operator at 52% market share, connects via dedicated SMPP links to international gateways and supports both GSM-7 and UCS-2. Ooredoo Palestine (48% market share) also supports both encodings but may deprioritize non-preferred senders during congestion. Both operators' SMSC nodes enforce a 160-character GSM-7 / 70-character UCS-2 limit per segment and honor international concatenation headers for multi-segment messages.

Operator routing is stable within the West Bank (direct PTA-regulated interconnect). Gaza routing is less stable and passes through Jawwal's internal relay, introducing variable latency and periodic disruptions tied to regional infrastructure conditions. smsroute.cc maintains redundant routes to both operators to maximize delivery success, but users targeting Gaza should account for potential delays.

Consent Framework and Regulatory Requirements in Palestine

The Palestinian Telecom Authority (PTA), headquartered in Ramallah, publishes the PTA Regulations which govern A2P SMS services. Additionally, the Palestinian Data Protection Law (in draft as of 2024) establishes consent requirements for marketing communications. The PTA authority is contested between West Bank (de jure PTA) and Gaza (de facto Jawwal), but both regions enforce explicit opt-in consent for marketing SMS.

Explicit opt-in means the recipient must affirmatively agree to receive marketing SMS — not passive consent, not pre-checked boxes, and not silent acceptance. The PTA does not recognize soft opt-in (e.g., consent via purchase without explicit SMS confirmation). Your opt-in records must be retained for at least 12 months and made available to the PTA upon request.

Transactional SMS (order confirmations, password resets, appointment reminders, account statements) are exempt from the opt-in requirement if they are triggered by the recipient's prior action and contain no promotional content. However, the PTA has broad discretion to classify ambiguous messages as marketing; appending a promotional footer or unsubscribe link to a transactional message may trigger reclassification to marketing, which requires opt-in.

The PTA does not publish specific enforcement fines or public cases, but the regulator has authority to issue cease-and-desist orders, require carrier blocking, and mandate corrective advertising. We recommend maintaining audit trails of all consent records, quiet-hour compliance, and sender-ID approvals. If you send marketing SMS without documented opt-in, you risk carrier blocking and account suspension.

Mobile Operators and Market Coverage

Jawwal (Palestinian Cellular Communications) — 52% market share. Jawwal is the oldest and largest mobile carrier in Palestine, operating since 1999 under a license from the PTA. Jawwal serves approximately 3.1 million active subscribers and operates GSM/LTE networks in both the West Bank and Gaza. Jawwal accepts SMPP connections from international gateways with pre-approved sender IDs and maintains direct interconnect to smsroute.cc.

Ooredoo Palestine — 48% market share. Ooredoo (formerly Wataniya Palestine) is a subsidiary of the Ooredoo Group and holds a PTA license. Ooredoo serves approximately 2.9 million active subscribers and operates LTE networks primarily in the West Bank, with limited coverage in Gaza. Ooredoo also accepts SMPP from international gateways and maintains interconnect to smsroute.cc. Ooredoo subscribers receive comparable delivery and latency to Jawwal subscribers.

Both operators support A2P SMS delivery and require pre-approved alphanumeric sender IDs. Numeric sender IDs (shortcodes) are not available for international senders. smsroute.cc manages the sender-ID registration process with both operators through the PTA (West Bank) or Jawwal (Gaza). Typical approval time is 4–5 business days for West Bank registrations; Gaza approvals may take longer due to de facto administrative delays.

How to Send SMS to Palestine in 3 Steps

Step 1: Create a free account

Visit smsroute.cc and sign up with your email address. You will not be asked for phone verification, government ID, or corporate documentation. Account activation is instant. You receive an API key and access to the web console immediately.

Step 2: Top up with cryptocurrency

Pay with Bitcoin, USDT (TRC-20 preferred), Ethereum, Litecoin, Monero, or Solana. No cards, no SEPA transfers, no bank wire required. Minimum top-up is $5 USD equivalent. Funds settle in 1–3 blockchain confirmations and are immediately available for SMS sending.

Step 3: Send SMS to Palestine

Use the REST API, SMPP protocol, or the web console. Address Palestinian phone numbers in E.164 format: +970 5XX XXX XXXX or +970 569 XXXX (Jawwal and Ooredoo mobile prefixes). Include your pre-approved sender ID (alphanumeric, max 11 characters, Arabic or English). Track delivery status in the dashboard or via webhook callbacks.

REST API Example (curl)

Python SDK Example

Both methods return a unique message ID and initial delivery status. You can poll the status endpoint or listen for webhook callbacks (configured in the dashboard) to track final delivery. Successful delivery to the recipient's device is confirmed within 10 seconds in most cases.

curl -X POST https://api.smsroute.cc/send \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "to": "+970512345678",
    "from": "YourBrand",
    "text": "Hello from smsroute.cc",
    "route": "standard"
  }'

import smsroute

client = smsroute.Client(api_key="YOUR_API_KEY")

response = client.sms.send(
    to="+970512345678",
    from_="YourBrand",
    text="Hello from smsroute.cc",
    route="standard"
)

print(response.status)  # "delivered" or "pending"
print(response.message_id)

import fetch from "node-fetch";

const apiKey = process.env.SMSROUTE_API_KEY;

const res = await fetch("https://api.smsroute.cc/messages", {
  method: "POST",
  headers: {
    Authorization: `Bearer ${apiKey}`,
    "Content-Type": "application/json",
  },
  body: JSON.stringify({
    to: "+9705551234567",
    from: "smsroute",
    text: "Your verification code is 384921",
  }),
});

console.log(await res.json());

<?php
$apiKey = getenv('SMSROUTE_API_KEY');

$payload = json_encode([
    'to'   => '+9705551234567',
    'from' => 'smsroute',
    'text' => 'Your verification code is 384921',
], JSON_UNESCAPED_UNICODE);

$ch = curl_init('https://api.smsroute.cc/messages');
curl_setopt_array($ch, [
    CURLOPT_POST => true,
    CURLOPT_RETURNTRANSFER => true,
    CURLOPT_HTTPHEADER => [
        'Authorization: Bearer ' . $apiKey,
        'Content-Type: application/json',
    ],
    CURLOPT_POSTFIELDS => $payload,
]);

echo curl_exec($ch);
curl_close($ch);

package main

import (
    "bytes"
    "encoding/json"
    "fmt"
    "io"
    "net/http"
    "os"
)

func main() {
    payload, _ := json.Marshal(map[string]string{
        "to":   "+9705551234567",
        "from": "smsroute",
        "text": "Your verification code is 384921",
    })

    req, _ := http.NewRequest("POST",
        "https://api.smsroute.cc/messages",
        bytes.NewBuffer(payload))
    req.Header.Set("Authorization", "Bearer "+os.Getenv("SMSROUTE_API_KEY"))
    req.Header.Set("Content-Type", "application/json")

    resp, err := http.DefaultClient.Do(req)
    if err != nil { panic(err) }
    defer resp.Body.Close()

    body, _ := io.ReadAll(resp.Body)
    fmt.Println(string(body))
}