SMS Gateway API: How to Send SMS Directly from Your Own Systems

ByStian Pedersen

Table of contents

Make SMS Gateway API

With an SMS gateway API, your core system, online store, or app can send and receive SMS messages automatically, without anyone clicking "send". Here is a practical overview of how it works, what to look for in a provider, which regulations apply in Norway, and how to get started with Make.

What is an SMS gateway API?

An SMS gateway connects your software to mobile networks. Your system sends a message to the gateway, which formats it correctly and routes it to the recipient's carrier. Replies from the recipient follow the same path back.

The API is the interface your system uses to communicate with the gateway. With Make, this uses standard web requests: you send an HTTP POST with JSON over HTTPS, and you receive standard HTTP status codes in return. As a result, it works with any programming language and platform you already use.

Typical use cases

SMS works best when messages are short, important, and time-critical:

  • Alerts and operational updates: Power outages, changes in opening hours, or incidents requiring immediate action.

  • Reminders: Appointments, deadlines, and package pickups.

  • Order and delivery confirmations: Triggered automatically by events in your e-commerce or ERP platform.

  • One-time passcodes (OTP/2FA): Logins and phone number verification.

  • Two-way communication: Confirmations, cancellations, registrations, and voting.

  • Marketing: Campaigns and offers, sent only to recipients who have given consent (more details below).

Key features of a reliable SMS API

Straightforward integration and bulk support

Integration should not require an extensive development project. The Make SMS Gateway API lets you send multiple messages in a single request, allowing both bulk SMS and single alerts to run through the same interface. The API supports both text and binary messages.

Reliable delivery reports

Sending an SMS is straightforward. Knowing what actually arrived is what separates an amateur setup from a professional gateway. With Make, you receive a delivery report (DLR) for every message sent to a URL you specify, complete with detailed status codes such as delivered, in transit, blocked, invalid number, or expired. Reports automatically retry if your receiving endpoint does not respond. You can also define an expiration time for messages, ensuring a one-time code is not delivered after it has expired.

Two-way SMS

Incoming SMS (MO, "mobile originated") messages are forwarded directly to your URL, bringing replies straight into your system. Make supports alphanumeric sender IDs, dedicated or shared short codes, keywords for replies, and both domestic and international numbers. For specialized requirements, premium rate (reverse billing) and age verification options are also available.

Security and operational reliability

All traffic is encrypted using HTTPS, and delivery reports can be secured with Basic auth. Make also provides dual endpoints, ensuring message delivery continues even if one endpoint is unreachable. We recommend building your integration to fall back to the backup endpoint automatically.

Characters, Unicode, and message parts: what many overlook

A standard SMS contains up to 160 characters when the text uses the GSM 7-bit alphabet. If a message includes characters outside this character set, it is sent as Unicode, and the limit drops to 70 characters. Longer messages are split into multiple parts, where each segment holds up to 153 characters (GSM-7) or 67 characters (Unicode), as header data is needed to reassemble the parts on the receiving device.

Two details are particularly useful for Norwegian senders:

  • Æ, ø, and å are included in the GSM-7 alphabet. Using Norwegian letters alone does not make the message more expensive.

  • A single emoji or "curly" quote mark is enough to force the entire message into Unicode. The euro sign (€) and a few other symbols count as two characters.

Make automatically sends messages as Unicode when required, ensuring text displays correctly. Long messages are split automatically. If you want to minimize the number of SMS parts used, Make can automatically replace special characters with equivalent standard characters.

Sender ID: use your company name

With Make, you can use an alphanumeric sender ID of up to 11 characters instead of a phone number. Note that recipients cannot reply to a text-based sender ID. If you need two-way communication, you must use a dedicated number or a keyword tied to a short code.

Stick to the letters A–Z, numbers 0–9, and the characters &, #, and !. Avoid æ, ø, å, and spaces, as carrier support for them varies.

Tip: Protect your sender ID against fraud
Fraudsters often send SMS messages impersonating well-known brands. The Norwegian Communications Authority (Nkom) and Økokrim recommend registering your sender ID in the SMS SenderID registry. Several mobile operators offer this service. Registering places your sender name on an approved whitelist, blocking spoofed messages that attempt to use your identity.

Regulations you need to know

Marketing requires prior consent

Under Section 15 of the Norwegian Marketing Control Act, you cannot send promotional SMS or email messages to individual consumers without their prior consent. That consent must be:

  • Freely given: The individual must have a genuine choice. You cannot make marketing consent a condition of purchase.

  • Explicit: The individual must take an active step, such as checking an opt-in box. Pre-ticked boxes are not valid.

  • Informed: The individual must clearly understand who is sending the message, what content it covers, and how to opt out.

Two common pitfalls to avoid:

  • You cannot send an SMS asking for consent. That request is legally classified as marketing in itself.

  • Consent given for email does not cover SMS. You must obtain consent for each specific channel.

Exception for existing customers: If you have an active customer relationship, such as an ongoing subscription or membership, you may send offers for similar products without prior consent. However, the customer must have been given an opt-out opportunity when their number was collected, and every message must provide an easy way to unsubscribe.

Service notifications are not marketing: Order confirmations, appointment reminders, and delivery alerts can be sent without marketing consent. However, adding promotional content or offers turns the message into marketing.

Non-compliance carries financial risk: The Norwegian Consumer Authority can issue injunctions and coercive fines per illegal message sent. Learn more in the Consumer Authority guidelines.

GDPR

Phone numbers constitute personal data. When using a third-party provider to send SMS, you must have a data processing agreement in place. Make stores all personal data on servers located in Norway.

SMS for one-time passcodes

While SMS is widely used for authentication and verification, it is not the most secure method available. NIST considers SMS codes an out-of-band method with known vulnerabilities and advises caution. Set short expiration windows for codes, and consider stronger alternatives, such as authenticator apps, where security requirements are high.

How to get started with the Make SMS Gateway API

  1. Request access. Email support@make.as or schedule an introductory demo via the product page.

  2. Receive your account and credentials. You will receive a Make SMS Gateway account with API credentials.

  3. Choose your sender configuration. Select an alphanumeric sender ID of up to 11 characters, or a dedicated number or keyword if you require replies.

  4. Set up endpoints. Create endpoints to receive delivery reports (DLR) and incoming messages (MO), and secure your DLR endpoint with Basic auth.

  5. Test and configure error handling. Send test messages, verify HTTP status codes, and ensure automatic failover to the secondary endpoint.

  6. Move to production. Ensure all consent records and opt-out lists are verified for any promotional traffic.

Frequently asked questions about SMS gateway APIs

What is the difference between an SMS gateway and an SMS API? The SMS gateway is the underlying service that routes and delivers messages into mobile networks. The API is the software interface your systems use to send and receive messages through that gateway.

Can I send bulk SMS through the API? Yes. The Make SMS Gateway API allows you to send multiple messages within a single request.

How do I verify that an SMS was delivered? You receive a delivery report (DLR) for each message posted back to your URL, detailing statuses such as delivered, in transit, blocked, invalid number, or expired.

Can we use our company name as the sender ID? Yes, you can use an alphanumeric sender ID of up to 11 characters. If you want recipients to be able to reply, you must use a dedicated number or a keyword on a short code instead.

Do æ, ø, å, or emojis incur extra charges? Æ, ø, and å are included in the standard GSM-7 character set and do not increase costs. Emojis and certain special symbols switch the message encoding to Unicode, which reduces the character limit from 160 to 70 characters per SMS part.

Do I need consent to send SMS messages? For promotional messages, yes, as a general rule. Pure service notifications like order confirmations and reminders do not require marketing consent, though you still need a lawful basis under GDPR to process the personal data.

Ready to connect your systems to Make?

Explore our features, or book a consultation to see how the API fits into your technical setup.

Get started with a 30-day trial

Get started with a 30-day trial