SMS Gateway Platform

Dashboard

Real-time platform overview

connecting...

Refresh

0

Messages Today

0

Delivered Today

0

Failed Today

0

Queued

0

SMPP Connectors

0

HTTP Connectors

0

Active Users

0

Current Total Credit Usage

0

Running Campaigns

0

Credits Used Today

0%

Delivery Rate

0

Total Credits Assigned

Traffic (Last 24 Hours)

System Health

SMS Gateway

Checking...

RabbitMQ Broker

Checking...

Redis Cache

Running

PostgreSQL

Connected

SMPP Port 2775

Open

HTTP API

Active

Message Status

Weekly Traffic

Recent Activity

Activity will appear here

Failure Reasons Summary

No failures in selected period

Quick Actions

Top Enterprise Accounts

Account	Messages	Delivered	Failed	Rate

Top Routes / Connectors

Connector	Messages	Delivered	Failed	Rate

Message Logs

—

MT (Outbound)

—

MO (Inbound)

—

API Sent

—

Campaign Sent

ID	Dir	From	To	Message	Connector	Source	Campaign	User	Status	DLR	Enc	Credits	Error	Time
No messages yet

—

Delivery Reports

—

Total DLRs

—

Delivered

—

Failed

—

Pending

—

Expired

—

Avg Delay

Date Range By

From

To

Quick

Delayed only (>60s)

Message ID	Sender ID	MSISDN	DLR Status	Error	Connector	Delay	Submit Date	Done Date	Received	EA Account
Delivery reports appear here when DLR status updates are received

—

DLR Detail

Inbound SMS (MO)

0

Total Received

0

Today

0

Forwarded OK

0

Forward Failed

0

Auto Replied

0

Shortcodes

Search

Connector

Shortcode

From

To

From	To / Short Code	Message	Connector	Routed To	Fwd Status	Time
Inbound messages will appear here

Test Inbound SMS (Simulate deliver_sm)

Simulate an MO (mobile-originated) message to test shortcode matching, auto-reply, forwarding, and enterprise inbox routing — without sending from a real phone.

From (Sender) *

To (Shortcode) *

Message *

Send SMS

Routing Profile

Auto-selects connector & sender based on destination

Encoding

Arabic, Chinese & special chars auto-switch to Unicode

To (MSISDN) *

From (Sender ID)

Leave blank to use routing profile sender

Message *

0 chars · 1 SMS

SMPP Client Connectors

—

Total

—

Running

—

Stopped

—

Low Balance

—

Near Limit

—

Queued

Connector ID	Provider	Host	Port	Username	Bind	Status	Throughput	Billing	Balance / Quota	Usage Month	Balance State	Window	Queued	Last Submit	Last DLR	Actions

HTTP Connectors

—

Total

—

Active

—

Inactive

—

Low Balance

—

Near Limit

—

Queued

Connector ID	Provider	Base URL	Method	Status	Billing	Balance / Quota	Usage Month	Balance State	Window	Queued	Created	Actions

MT (Outbound) Routes

MT Routing (Mobile Terminated) controls outbound SMS delivery — messages going to mobile phones. Routes decide which SMPP connector to use for each outbound message based on filters (destination prefix, source, user, etc.). Lower order = higher priority.
⚠️ Routing Profiles (Gateway → Routing Profiles) are the recommended way for per-client routing — they wrap MT routes with prefix tables and auto-assign connectors per destination. Use raw MT routes only for system-wide defaults or advanced bypass rules.

Order	Details	Actions

MO (Inbound) Routes

MO Routing (Mobile Originated) handles inbound SMS — messages sent from mobile phones to your short codes via an SMPP connector. Each route specifies: which SMPP connector receives the message, which user's inbox it goes to, and (optionally) an HTTP URL to forward the message to an external system.

Order	SMPP Connector	Inbox User	HTTP Forward	Details	Actions

Routing Filters

Filter ID	Details	Actions

Routing Profiles

Define number-prefix routing rules with connector and sender ID mappings. Assign profiles to users and API accounts.

—

Total Profiles

—

Active

—

Inactive

—

Total Routes

—

Assigned Users

—

API Accounts

—

With Warnings

Sender IDs

Manage sender IDs linked to routing profiles and connectors

0 total

0 active

0 linked to profiles

0 assigned to EAs

Sender ID	Status	Type	Routing Profiles	Connectors	EAs	Created	Actions
No sender IDs registered

Blacklist / Opt-Out

Numbers that are blocked from receiving SMS messages

Phone Number	Reason	Active	Added	Actions
No blacklisted numbers

MNO / Number Portability Prefixes

Lookup table for mobile network operator identification by number prefix

Search Operator / Prefix

Country Code

Prefix	Operator	Country	MCC	MNC	Actions
No prefixes configured. Add prefixes for MNO identification.

SMS Campaigns

Name	Routing Profile	Sender	Recipients	Progress	Status	Created By	Created	Actions

Campaign Monitor

Loading...

Routing Profile: —

Sender: —

Created By: —

Credits Used: 0

0

Total

0

Submitted

0

Delivered

0

Awaiting DLR

0

Failed

0

Queued

0

Credits

Progress0%

Live Activity

Number	Status	DLR	Connector	Error / Details	Sent	Delivered
Waiting for activity...

Campaign Templates

Name	Message Preview	Sender ID	Created	Actions
Create message templates for quick campaign setup

Number Lists

Name	Description	Numbers	Created	Actions
Upload or create number lists for campaigns

Campaign A/B Tests

Split-test two campaign variants to compare delivery performance

Name	Campaign A	Campaign B	Split	Status	A Delivery	B Delivery	Actions
No A/B tests yet. Create one to compare two campaign variants.

Groups

Group ID	Actions

Enterprise Users

—

Total

—

Active

—

Suspended

—

With Credits

—

With Routing

—

With Perm Group

Username	Company	Perm Group	Routing	Sender IDs	Credits	TPS	Bindings	Status	Created	Actions

Permission Groups

Define role-based access groups and assign them to Enterprise Users

Group Name	Description	Status	Permissions	Users	Created	Actions

Credits & Wallet

Manage credit balances, top-ups, deductions, and transaction ledger for all accounts

—

Total Credits

—

Used Today

—

Added Today

—

Low Balance

—

Wallet Accounts

—

Unlimited

Wallet Accounts

Account	Company	Balance	Today	Month	Mode	Last Top-up	Status	Actions

Transaction Ledger

Full audit trail of all credit movements

Date	Account	Type	Amount	Before	After	Description	Source	By	Ref
No transactions yet

Invoices

Generate and manage billing invoices based on credit usage

Invoice #	Account	Period	Amount	Status	Generated	Actions
No invoices yet. Generate one from the credit transaction history.

API Keys

Use API keys to send SMS programmatically. POST /panel/api/v1/send with header X-API-Key: your_key

Name	Key Prefix	Owner	Status	Last Used	Created	Actions
No API keys generated

Webhooks

Name	URL	Events	Status	Actions
Configure webhooks for DLR and MO notifications

Admin Users

Username	Role	Created	Actions

Audit Logs

Action Filter

From

To

Limit

#	Time	User	Action	Entity	ID	IP	Details
Audit trail will appear after actions are performed

System Settings

Branding & Identity

Platform / Company Name

Company Legal Name

System Logo

Upload Image

PNG / JPG / SVG · max 2 MB · shown in the panel header

Logo preview

Company Contact Details

Business Phone

Business Email

Support Email

Website

Business Address

Platform Configuration

Default Coding

Max SMS per Campaign

Default Throughput (msg/s)

System Timezone

All dates/times in the panel display in this timezone

Jasmin HTTP API Credentials

HTTP Username

HTTP Password

Used by Send SMS and Campaign engine to authenticate with Jasmin HTTP API

Alerts

Low Credit Alert Threshold

Alert when user credits drop below this amount

SMTP (Email Alerts)

SMTP Host

SMTP Port

SMTP Security

SMTP Username

SMTP Password

From Name

From Email

These values are saved in system settings and used for connector alert emails.

About

Platform	SMS Gateway v3.0
Core Engine	Jasmin SMS Gateway (Docker)
Architecture	Core System Architecture by Azhar
Components	Node.js, PostgreSQL, Redis, RabbitMQ, Nginx

Gateway CLI

Type help for commands. This is a direct jCLI session.

ESME / SMPP Client Accounts

Manage SMPP bind credentials for your clients and applications

System ID	Assigned User	Routing Profile	Max Binds	IP Whitelist	Status	Actions
No ESME accounts yet. Add one to allow SMPP client binds.

HTTP API Accounts

Enterprise-linked REST API credentials — each account uses its enterprise account's credits, routing, and message logs.

—

Total Accounts

—

Active

—

EA-Linked

—

With DLR URL

Username	Description	Enterprise Account	Credits	Rate	DLR URL	Status	API Key	Actions
No HTTP API accounts yet.

Shortcode Management

Create shortcodes, assign to enterprise accounts, configure auto-replies and forwarding

0

Total Shortcodes

0

Total Received

0

Received Today

0

Total Forwarded

Shortcode	Description	SMPP Connector	Assigned EA	Forward URL	Auto-Reply	Keywords	Received	Status	Actions
No shortcodes configured yet.

Route Tester / Simulator

Test how a destination number will be routed without sending a real message

Test Parameters

Destination Number *

Routing Profile

User (optional)

Result

Enter a destination number and click Run to test routing

Documentation & Guides

Complete step-by-step guides for administrators and enterprise clients. All examples are copy-paste ready.

1. HTTP API Account Setup

An HTTP API account provides credentials for your client application to send SMS via REST API. Each account has its own username, password, API key, rate limit, and credit balance.

Step-by-Step: Create an HTTP API Account

Navigate to Gateway → HTTP API Clients in the sidebar
Click Add HTTP API Account

Fill in the required fields:

Username	Unique identifier, e.g. `company_otp`. This is used for Basic Auth.
Password	Set a strong password. This is used for Basic Auth.
Routing Profile	Select which SMPP connector(s) to route through. Leave blank for default.
Rate Limit	Messages per second allowed (default: 10). Excess messages are queued automatically.
Credit Balance	Starting credits. Each SMS deducts 1 credit. Set 0 + check "Unlimited" for no limit.

(Optional) Under Enterprise Account Linking:
- Select the Enterprise user this API account belongs to
- Set a default Sender ID
- Set a DLR Webhook URL for delivery receipts
Click Save — the system auto-generates an API Key

Authentication Methods

Your client application can authenticate using any of these methods:

Option 1: API Key Header

X-API-Key: httpapi_abc123def456...

# The API key is shown after creating the account.
# Click the key icon in the table to copy it.

Option 2: HTTP Basic Auth

Authorization: Basic base64(username:password)

# Use the username and password you created.
# Most HTTP libraries support Basic Auth natively.

Option 3: URL Parameters

?user=USERNAME&password=PASSWORD

# Pass credentials as query params (GET or POST).
# Useful for simple integrations & legacy systems.

2. Sending SMS via API

Endpoints

POST /api/v1/http-send (JSON body)

GET /api/v1/http-send?user=USERNAME&password=PASSWORD&to=PHONE&content=MSG&from=SENDER (URL params)

Request Parameters (JSON body or URL query params)

Field	Type	Required	Description
`to`	string	Yes	Destination phone number in international format, e.g. `971501234567`
`content`	string	Yes	SMS message body (auto-splits long messages)
`from`	string	No	Sender ID (alphanumeric max 11 chars or numeric). Uses routing profile default if blank.
`coding`	string	No	`0` = GSM7 (English/Latin), `8` = UCS2 (Arabic/Unicode). Auto-detected if omitted.

cURL Example — English SMS (API Key)

curl -X POST /api/v1/http-send \
  -H "Content-Type: application/json" \
  -H "X-API-Key: YOUR_API_KEY" \
  -d '{
    "to": "971501234567",
    "content": "Your OTP code is 4829. Valid for 5 minutes.",
    "from": "MYCOMPANY"
  }'
          

GET — URL Parameter Style (Username/Password)

curl "/api/v1/http-send?user=YOUR_USERNAME&password=YOUR_PASSWORD&from=MYCOMPANY&to=971501234567&content=Hello+World&dr=1"
          

cURL Example — Arabic / Unicode SMS

curl -X POST /api/v1/http-send \
  -H "Content-Type: application/json" \
  -H "X-API-Key: YOUR_API_KEY" \
  -d '{
    "to": "971501234567",
    "content": "\u0645\u0631\u062d\u0628\u0627 \u0628\u0643\u0645 \u0641\u064a \u062e\u062f\u0645\u062a\u0646\u0627",
    "coding": "8"
  }'
          

PHP Example

<?php
\$url = '/api/v1/http-send';
\$data = [
    'to'      => '971501234567',
    'content' => 'Your verification code is 1234',
    'from'    => 'MYCOMPANY'
];

\$ch = curl_init(\$url);
curl_setopt_array(\$ch, [
    CURLOPT_POST           => true,
    CURLOPT_HTTPHEADER     => [
        'Content-Type: application/json',
        'X-API-Key: YOUR_API_KEY'
    ],
    CURLOPT_POSTFIELDS     => json_encode(\$data),
    CURLOPT_RETURNTRANSFER => true,
    CURLOPT_TIMEOUT        => 30
]);

\$response = json_decode(curl_exec(\$ch), true);
curl_close(\$ch);

if (\$response['ok']) {
    echo "SMS sent! Message ID: " . \$response['message_id'];
} else {
    echo "Error: " . \$response['error'];
}
?>
          

Python Example

import requests

url = "/api/v1/http-send"
headers = {
    "Content-Type": "application/json",
    "X-API-Key": "YOUR_API_KEY"
}
payload = {
    "to": "971501234567",
    "content": "Hello from Python!",
    "from": "MYAPP"
}

response = requests.post(url, json=payload, headers=headers)
data = response.json()

if data["ok"]:
    print(f"Sent! ID: {data['message_id']}")
else:
    print(f"Error: {data['error']}")
          

Node.js Example

const response = await fetch('/api/v1/http-send', {
  method: 'POST',
  headers: {
    'Content-Type': 'application/json',
    'X-API-Key': 'YOUR_API_KEY'
  },
  body: JSON.stringify({
    to: '971501234567',
    content: 'Hello from Node.js!',
    from: 'MYAPP'
  })
});
const data = await response.json();
console.log(data.ok ? 'Sent: ' + data.message_id : 'Error: ' + data.error);
          

Response

200 OK
{"ok":true,"message_id":"abc-def-789"}

400 {"ok":false,"error":"to and content required"}
401 {"ok":false,"error":"Invalid credentials"}
402 {"ok":false,"error":"Insufficient credits"}
200 {"ok":true,"queued":true,"message_id":"queued_..."} — Rate/daily limit exceeded, message queued

3. API Authentication Details

Which username and password to use?

Important: The HTTP API username/password are NOT the same as the panel login. They are a separate set of credentials created specifically for the API account under Gateway → HTTP API Clients.

Credential	Where to Find	Used For
API Key	Shown in HTTP API Clients table (click icon to copy)	Header: `X-API-Key`
API Username	The username you set when creating the HTTP API account	Basic Auth: `username:password`
API Password	The password you set when creating the HTTP API account	Basic Auth: `username:password`
Panel Username	Your login to this dashboard	NOT for API calls

Quick Test: After creating an API account, copy the API key and run this in your terminal:

curl -X POST /api/v1/http-send -H "Content-Type: application/json" -H "X-API-Key: PASTE_YOUR_KEY_HERE" -d '{"to":"971501234567","content":"Test"}'

4. How to Create a Shortcode

A shortcode (e.g., 3536) receives inbound SMS from mobile users. You can route messages to an enterprise inbox, forward to an external URL, and auto-reply — all at the same time.

Step-by-Step

Go to Gateway → Shortcodes in the sidebar
Click Add Shortcode

Fill in the form:

Shortcode *	The number that mobile users send SMS to (e.g., `3536`)
SMPP Connector *	Select the SMPP connector that handles this shortcode's traffic. This is the connection to the telco.
Assigned EA	Select an enterprise user. Inbound messages will appear in their inbox (Messaging → Inbound SMS). Leave blank for admin-only visibility.
Description	Optional label, e.g., "Marketing opt-in" or "Customer support"

Configure optional features (HTTP Forwarding, Auto-Reply) — see sections 5 and 6 below
Click Save Shortcode

How it works: When a mobile user sends an SMS to your shortcode, the SMPP connector receives it. The system matches the destination number to a shortcode, saves it to the inbox (always), then optionally forwards to your URL and/or sends an auto-reply.

Flow Diagram:
Mobile User → Telco → SMPP Connector → Shortcode Match → [Save to Inbox] + [Forward to URL] + [Auto-Reply]

5. How to Forward Inbound SMS to External URL

Enable Forwarding

Edit or create a shortcode
Toggle Enable HTTP Forwarding ON
Enter your server URL, e.g., https://your-app.com/inbound-sms
Save

What your server receives (POST JSON)

{
  "from": "971501234567",
  "to": "3536",
  "content": "HELP I need information about your service",
  "connector": "MAIN-SMPP",
  "message_id": "550e8400-e29b-41d4-a716-446655440000",
  "timestamp": "2026-04-10T12:30:00.000Z",
  "shortcode_id": 1,
  "ea_username": "company_user"
}
          

Building your endpoint

Your server must:

Accept POST requests with Content-Type: application/json
Return HTTP 2xx status to confirm receipt
Respond within 10 seconds (timeout)

Example PHP receiver

<?php
// inbound-sms.php — receive forwarded inbound SMS
\$payload = json_decode(file_get_contents('php://input'), true);

\$from     = \$payload['from'];      // Sender phone number
\$to       = \$payload['to'];        // Shortcode number
\$message  = \$payload['content'];   // SMS text
\$msgId    = \$payload['message_id'];

// Process the message (save to DB, trigger workflow, etc.)
file_put_contents('inbound_log.txt', date('c')." | From: \$from | To: \$to | Msg: \$message\n", FILE_APPEND);

// MUST return 2xx or it will be logged as failed forward
http_response_code(200);
echo json_encode(['status' => 'received']);
?>
          

Important: Messages are always saved to the system inbox regardless of forwarding. If your endpoint returns a non-2xx response, the failure is logged and visible in the Inbound SMS stats (Forward Failed count).

6. How to Set Up Auto-Reply & Keywords

Default Auto-Reply

Edit or create a shortcode
Toggle Enable Auto-Reply ON
Type a default reply message, e.g., "Thank you for contacting us! We'll respond shortly."
Save — every inbound SMS to this shortcode will now get this auto-reply

Keyword-Based Replies

You can set different replies for different keywords. The system checks the first word of the incoming message (case-insensitive).

In the shortcode table, click the Keywords button (shows count)
In the modal, type a keyword (e.g., HELP) and a reply message
Click Add Keyword Rule

How matching works

Incoming SMS	Keyword Match	Reply Sent
"HELP I need info"	HELP	Custom HELP reply
"help please"	HELP (case-insensitive)	Custom HELP reply
"INFO"	INFO	Custom INFO reply
"Hello there"	No keyword match	Default auto-reply message

Modes: You can combine Inbox + Forwarding + Auto-Reply in any combination:
• Inbox only — messages saved, no forwarding, no reply
• Inbox + Auto-Reply — messages saved + automatic responses
• Inbox + Forward + Auto-Reply — full pipeline (message saved, forwarded to URL, and reply sent)

7. How to Test a Shortcode Without Sending From a Phone

Use this to verify shortcode routing, auto-reply, and forwarding work correctly before going live.

Method 1: Use the Panel Test Form

Go to Messaging → Inbound SMS
Scroll down to Test Inbound SMS (Simulate deliver_sm)
Enter a From number (any), the shortcode in "To", and a test message
Click Send Test
The message flows through the full inbound pipeline: shortcode matching, inbox routing, forwarding, auto-reply

Method 2: Direct API Call

Use the /api/deliver_sm endpoint to simulate an inbound message programmatically:

# GET method (quick test):
curl "/api/deliver_sm?src=971508994714&dst=3536&msg=HELP"

# POST method (full control):
curl -X POST /api/deliver_sm \
  -H "Content-Type: application/json" \
  -d '{
    "src": "971508994714",
    "dst": "3536",
    "msg": "HELP I need information"
  }'
          

Parameters

Field	Required	Description
`src`	Yes	Source / sender phone number (simulated mobile number)
`msg`	Yes	Message content (the SMS text the "mobile user" sends)
`dst`	Recommended	Destination / shortcode number. If blank, the message is saved without shortcode matching.
`msg_id`	No	Custom message ID. Auto-generated UUID if blank.
`ea`	No	Enterprise account username override (bypasses shortcode EA assignment)
`type`	No	Message type (default: "sms")

What happens

Message is saved to inbox with connector = "test-deliver-sm"
If dst matches a shortcode: enterprise inbox routing activates
If forwarding is enabled: your external URL receives the POST
If auto-reply is enabled: the reply message is sent back via SMPP

8. DLR (Delivery Report) Callbacks

Setup

Set a DLR Webhook URL on the HTTP API account. When the carrier sends a delivery receipt, we forward it to your URL via HTTP POST with JSON body:

{
  "message_id": "abc123-def456",
  "from": "MYCOMPANY",
  "to": "971501234567",
  "msisdn": "971501234567",
  "status": "DELIVRD",
  "error_code": "000",
  "connector": "smpp_connector_1",
  "timestamp": "2026-04-10T12:30:00.000Z"
}
          

DLR Payload Fields

Field	Type	Description
`message_id`	string	Unique message identifier returned when SMS was sent
`from`	string	Sender ID / source address used when sending the SMS
`to`	string	Destination phone number the SMS was sent to
`msisdn`	string	Recipient MSISDN (same as `to`)
`status`	string	Delivery status: `DELIVRD`, `UNDELIV`, `REJECTD`, `EXPIRED`, `ENROUTE`
`error_code`	string	Error code from carrier (`000` = no error)
`connector`	string	SMPP connector that handled the message
`timestamp`	string	ISO 8601 timestamp when DLR was received

Status	Meaning
`DELIVRD`	Delivered to handset
`UNDELIV`	Undeliverable
`REJECTD`	Rejected by carrier
`EXPIRED`	TTL expired
`ENROUTE`	In transit

9. Sender ID & Unicode SMS

Sender ID

Alphanumeric: up to 11 characters (e.g., MYCOMPANY)
Numeric: full phone number (e.g., 971501234567)
If from field is provided in the API, it overrides the routing profile default

Unicode / Arabic

System auto-detects non-GSM characters and switches to UCS-2 encoding
GSM 7-bit: max 160 chars → Unicode: max 70 chars per SMS part
Force Unicode with "coding":"8"

10. Credits & Billing

How to assign credits clearly to EA accounts

Go to Accounts → Enterprise Users and create/select the EA user.
Set initial balance in the user form (Credit Balance) and save.
Go to Accounts → Credits & Wallet to top-up/debit with reason notes.
If this EA uses HTTP API, link the API account to the EA in Gateway → HTTP API Clients (EA Username field).
If needed, enable Unlimited Credits on EA to bypass credit checks.

Important: Message log credits_used follows the route rate (example 0.5500), while EA balance deduction is currently 1 credit per SMS unless unlimited.

Quick policy summary

Each SMS sent deducts 1 credit from the EA/account balance (unless Unlimited).
Route rate (Routing Profiles) is logged as credits_used for reporting and costing.
Admin manages manual top-ups/debits via Credits & Wallet.
Enterprise user sees own balance in the header and credits page.

Connector commercial fields (SMPP + HTTP)

Open Gateway → SMPP Connectors or Gateway → HTTP Connectors, then Add/Edit connector and fill Provider Billing & Limits:

Field	Meaning	Stored As (DB)
Cost / SMS	Provider cost per message for reporting	`connector_profiles.cost_per_message`
Current Balance	Provider prepaid balance	`connector_profiles.current_provider_balance`
Monthly Limit	Postpaid monthly cap	`connector_profiles.monthly_limit`

Save on connector form writes to connector_profiles and is reflected in SMPP/HTTP connector lists and policy engine.

Alert triggers and channels

Prepaid alerts: Low/Critical/Exhausted trigger when current_provider_balance crosses thresholds.
Postpaid alerts: Warning/Critical/100% trigger when monthly usage crosses configured percentages.
SMS alert API: alerts are sent through Jasmin HTTP API endpoint http://smsplus-jasmin:1401/send using Settings → Jasmin HTTP user/password.
Email alerts: sent to connector alert_email_recipients using SMTP settings configured in System Settings → SMTP (Email Alerts).
Cooldown: repeats are suppressed by connector cooldown minutes unless alert level changes.

11. Enterprise Account Setup

Creating an Enterprise User

Go to Accounts → Enterprise Users → Click Add User
Set username, password, group, SMS quota, credit balance

Create a Permission Group to control visibility:

`view_logs`	Message logs, DLR, Inbound SMS, Shortcodes
`send_sms`	Send SMS page
`manage_campaigns`	Campaigns, Templates, Number Lists
`manage_api_keys`	API Keys
`manage_webhooks`	Webhooks

Enterprise users see only their own data (message logs, inbound, campaigns, credits)

EA + API + Credits mapping checklist

Create EA user and assign permissions/group.
Create HTTP API account and set EA Username to link billing and logs.
Assign routing profile to control connector selection and route rate.
Top-up EA credits in Credits & Wallet and keep threshold policy documented.
Optionally set low credit threshold in System Settings for dashboard alerts.

12. Troubleshooting

Problem	Solution
API returns `401`	Check API key or username/password. Make sure you’re using the HTTP API account credentials, not panel login.
API returns `402`	Add credits or enable Unlimited Credits on the account.
API returns `429`	Sending too fast. Reduce rate or increase the account’s rate limit.
SMS not delivered	Check DLR reports. Verify the SMPP connector is started and the MT route exists.
Arabic text garbled	Set `"coding":"8"` in the request or let auto-detect handle it.
Inbound SMS not received	Verify: shortcode exists, SMPP connector is active/started, MO route is configured.
Forward webhook failing	Ensure URL is accessible, returns 2xx within 10s. Check Forward Failed count in Inbound SMS stats.
Shortcode not matching	The destination number of the incoming SMS must exactly match the shortcode value. Use Test Inbound to verify.
Auto-reply not sending	Ensure Auto-Reply is enabled on the shortcode AND at least one SMPP connector is started for outbound.

Gateway Control

Monitor and manage services (Super Admin only)

—

CPU Usage

—

Memory Usage

—

Disk Usage

Docker Services

Service	State	Uptime	Ports	Actions

SMS Gateway

Dashboard

Traffic (Last 24 Hours)

System Health

Campaign Summary

Message Status

Weekly Traffic

Recent Activity

Failure Reasons Summary

Quick Actions

Top Enterprise Accounts

Top Routes / Connectors

Recent Errors (Last 24h)

Message Logs

Delivery Reports

DLR Detail

DLR Raw Payloads (last 20)

Inbound SMS (MO)

Test Inbound SMS (Simulate deliver_sm)

Send SMS

SMPP Client Connectors

Connector Logs — —

Connector Diagnostics — —

HTTP Connectors

MT (Outbound) Routes

MO (Inbound) Routes

Routing Filters

Routing Profiles

Sender IDs

Blacklist / Opt-Out

MNO / Number Portability Prefixes

SMS Campaigns

Campaign Monitor

Live Activity

Failure Summary

Send Errors

Campaign Templates

Number Lists

Campaign A/B Tests

Groups

Enterprise Users

Permission Groups

Credits & Wallet

Transaction Ledger

Invoices

API Keys

Webhooks

Admin Users

Audit Logs

System Settings

Branding & Identity

Company Contact Details

Platform Configuration

Jasmin HTTP API Credentials

Alerts

SMTP (Email Alerts)

About

Gateway CLI

ESME / SMPP Client Accounts

HTTP API Accounts

Shortcode Management

Add Shortcode

Keyword Auto-Replies

Route Tester / Simulator

Test Parameters

Result

Documentation & Guides

Table of Contents

1. HTTP API Account Setup

Step-by-Step: Create an HTTP API Account

Authentication Methods

2. Sending SMS via API

Endpoints

Request Parameters (JSON body or URL query params)

cURL Example — English SMS (API Key)

GET — URL Parameter Style (Username/Password)

cURL Example — Arabic / Unicode SMS

PHP Example

Python Example

Node.js Example