SMS API for systems and applications

Your application server sends using the account credential and authentication method in the approved integration documentation. Never place credentials in public JavaScript, analytics URLs or source control. Redact credentials and OTP content from request logs and use HTTPS.

A send request contains the account key api-token, sender name SenderText, mobile number MobileNumber and text MessageBody. Keep the endpoint and key in server settings. Check the HTTP status and success value after sending, then follow delivery reporting. Your integration documentation describes response fields and message identifiers.

• ✓Normalize Jordanian mobiles to 962 followed by the number without its local leading zero.
• ✓Test Arabic, mixed text and segmentation before estimating costs.
• ✓Link your business reference to the message identifier available in the response.

const url = new URL(process.env.SMS_SEND_URL);
url.search = new URLSearchParams({
  "api-token": process.env.SMS_TOKEN,
  SenderText: approvedSender,
  MobileNumber: recipient,
  MessageBody: messageText
}).toString();

const response = await fetch(url, {
  redirect: "error",
  signal: AbortSignal.timeout(10000)
});
const result = await response.json();
if (!response.ok || result.success !== true) {
  throw new Error("Submission not confirmed");
}