Can I send an SMS with a GET request, or do I need POST?

Use POST. The REST endpoint POST /sms/sendSms takes a JSON body and a Bearer token, so the message text and credentials never appear in URLs or server logs. The legacy HTTP API (/websmpp/websms) still accepts GET for existing SMPP-era integrations, but new integrations should use the REST API.

Do I need SMPP, or is the HTTP API enough?

The REST/HTTP API is enough for most volumes and is the fastest to integrate. SMPP suits very high sustained throughput and persistent binds. The same BroadNet account works over both, so you can start on HTTP and add SMPP later without re-onboarding.

How do I know a message was actually delivered?

Submission returns a message ID; the final handset status arrives asynchronously as a delivery receipt (DLR) on your webhook — delivered, failed, or expired. Don't treat the submission response as proof of delivery.

Operations BroadNet answer

How do you send an SMS via API?

Last reviewed September 24, 20261 min readReviewed by BroadNet engineering

Quick answer

Sending an SMS through an HTTP API means passing the destination number, sender ID, and message text to a REST endpoint that hands the message to operator networks and returns a message ID you can track for delivery.

Plain-language definitionVendor-neutralReviewed September 24, 2026

DiagramHow an A2P message reaches the phone

Your applicationSends over the REST API or SMPP
BroadNet platformValidates, routes and bills each message
Operator SMSCDirect operator connection
Subscriber handsetThe message is delivered

The delivery receipt (DLR) travels back along the same path to your webhook

The long answer

Everything worth knowing, nothing that isn't.

§01

The request

BroadNet's gateway accepts a POST to https://api.broadnet.me/sms/sendSms with an Authorization: Bearer token and a JSON body: senderId (the sender ID), destinationNumber (the destination number in international format, digits only, no plus sign), message (the text), and messageType (TEXT for GSM-7, UNICODE for Arabic, emoji and other non-Latin scripts). A successful call returns 200 OK with the message ID in the response body.

§02

Encoding and length

A GSM-7 message fits 160 characters per segment (153 once a message spans multiple segments); switching to Unicode for emoji or non-Latin scripts drops that to 70 (67 concatenated). Set messageType to TEXT for plain GSM-7 and UNICODE when the body needs Unicode or Arabic, so characters aren't garbled — POST /sms/identify returns the encoding and segment count before you send.

§03

Track delivery, don't assume it

The returned message ID is the handle for delivery receipts (DLRs). Configure a webhook to receive the operator's final status — delivered, failed, or expired — rather than treating a 200 on submission as proof the handset received the message.

§04

Moving to production

Use international E.164 numbers, register your sender ID in each destination market before you scale, and send over direct operator routes for consistent latency. For high volume the same account is reachable over SMPP as well as REST, so you can start on HTTP and switch bind types without re-onboarding.

BNWritten by the BroadNet engineering team·Operating carrier-grade messaging since 2003, headquartered in Dubai·Editorial standards

FAQ

Frequently asked questions

Can I send an SMS with a GET request, or do I need POST?: Use POST. The REST endpoint POST /sms/sendSms takes a JSON body and a Bearer token, so the message text and credentials never appear in URLs or server logs. The legacy HTTP API (/websmpp/websms) still accepts GET for existing SMPP-era integrations, but new integrations should use the REST API.
Do I need SMPP, or is the HTTP API enough?: The REST/HTTP API is enough for most volumes and is the fastest to integrate. SMPP suits very high sustained throughput and persistent binds. The same BroadNet account works over both, so you can start on HTTP and add SMPP later without re-onboarding.
How do I know a message was actually delivered?: Submission returns a message ID; the final handset status arrives asynchronously as a delivery receipt (DLR) on your webhook — delivered, failed, or expired. Don't treat the submission response as proof of delivery.

Build with this

Need help wiring this up?

The pages below are the products and integration guides that put this concept on the wire. If you'd rather walk through it live, our engineering team takes calls same-day during MENA working hours.

Talk to our engineering team

Feedback

Was this answer helpful?

Your vote helps us prioritise which answers to expand with examples, diagrams, and code snippets.

Yes No

Thanks — noted. We'll keep this answer maintained.

Got it. Tell us what was missing — send a quick note.

How we write and review content

Talk to a real engineer about your build.

We reply within one business day, and production accounts get 24/7 support. Our solutions engineers ship code, not scripts.

Talk to support Speak with sales

$ curl -X POST https://api.broadnet.me/sms/sendSms

Response SLA

Test-access requestsReply within 1 business day

Production24 / 7 · < 15 min

Operator NOC24 / 7 · pager

support@broadnet.me · +971 4 456 7768