SMS API

SMS API for business – send from your systems

Send SMS from your systems with the Intellipush SMS API. REST API, OAuth 2.0 and public documentation for reminders, confirmations and alerts. API access included.

Create a free account Open API documentation

OAuth 2.0

Use the current documentation to authenticate the integration and manage access.

REST API

Connect SMS to events and workflows in your own system.

API access included

Every account includes API access and open developer documentation.

Practical overview

SMS API: connecting your system to the recipient

An SMS API lets your software request a text message without someone writing it manually in the portal. Intellipush acts as an SMS gateway between your system and SMS delivery. Use the REST API for appointment reminders, order confirmations and alerts, and follow up available delivery status: creating a message is not the same as delivering it.

The API is for SMS that forms part of an existing process: an order is created, an appointment approaches or an agreed system event needs a concise alert. Your integration retains the business logic and uses Intellipush for the SMS flow.

First decide which events should trigger a message, what data the message needs and how consent or another lawful basis is documented. Also decide how the system should react when a request is rejected or cannot be completed. The current API documentation is always authoritative for endpoints, fields and responses.

Before production use, give the whole path a clear owner. Decide who may change message wording, who responds to technical failures and how delivery can be stopped if an event or recipient list proves incorrect. These decisions make the integration easier to operate over time.

Workflow

An integration your team can understand and operate

Build it in clear layers and test the whole path before production use.

01
Plan events and ownership
Describe when SMS should be sent, who owns the wording and what happens when delivery cannot be initiated.
02
Authenticate from the documentation
Use OAuth 2.0 as currently documented. Keep access details out of source code and restrict who can use them.
03
Build and validate the request
Normalise recipient numbers, check required fields and avoid sending more personal data than the message requires.
04
Handle responses and failures
Distinguish accepted requests from errors. Log technical references that support diagnosis, but not message content without a documented need.
05
Test before scaling
Use your own test recipients, low volumes and representative failures. Check that retries cannot create unintended duplicate messages.

For software and SaaS providers

Building software for multiple business customers?

Add SMS to the software you provide to multiple business customers. Connect reminders, confirmations and alerts to your customers’ workflows through one integration with the Intellipush SMS API.

The API supports creating and updating subaccounts where the feature is enabled. Contact us to discuss account setup, expected volume and billing for your solution.

Talk to us about your integration

REST API

The documentation is the technical contract

Always implement endpoints, fields and responses from the current API documentation. If you need to clarify solution design or expected volume, we can review the technical approach with you.

Sending higher SMS volumes? Monthly invoicing based on actual usage can be arranged.Discuss invoicing with us →

Open API documentation ↗OpenAPI YAML Talk to the technical team

OAuth 2.0

POST /restv2/sms/create
Authorization: Bearer <access_token>
Content-Type: application/json

{
  "message": "Your appointment is confirmed.",
  "countrycode": "+47",
  "phonenumber": "12345678"
}

We serve businesses in Norway and Europe. SMS destinations, sender types and optional features must be checked for the country and account setup you intend to use.

Next steps for your integration

Before you start

SMS API integration: practical questions before you start

Move from a first request to an integration your team can operate. Use current documentation for endpoints and fields, with business rules controlled by your own system.

How do we send our first SMS through the API?

Obtain an access token using OAuth 2.0 client credentials, then create one SMS from your server. Keep the API Secret and token out of browser code. Use your own test number and a low volume: a real creation request may consume SMS credits. Check the current contract before using the code.

See SMS API examples in cURL, PHP, Python, Node.js and C# →

Is an SMS API the same as an SMS gateway?

The terms describe different parts of the connection: an API is the interface your software uses, while a gateway connects its request to SMS delivery. Intellipush provides a REST API for organisations automating sending. API access does not mean that a ready-made plugin exists for every system.

Understand what an SMS gateway does →

How should we handle failures and delivery status?

Distinguish a rejected request, a created message and a later delivery outcome. Retain the message ID and check status using documented functionality. Test expired tokens, incorrect numbers and repeated requests. Do not build automatic retries that can create duplicate messages.

Read about SMS statuses and troubleshooting →

What should we clarify about cost and recipient data?

API access is included with every account. Sending costs depend on factors including destination and segments, with separate terms for optional services. Clarify recipient permission, the Data Processing Agreement and sender setup before moving personal data. Choosing an API does not guarantee compliance.

Follow the developer guide from token to first message →

In practice