SMS API

Integrate SMS into the systems you already use

Connect SMS to your own systems using the REST API and OAuth 2.0. API access is included with every account, with no separate monthly fee or lock-in.

Create a free account Open API documentation

No monthly platform fee
No lock-in
SMS credits valid for 24 months

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

Let the system send when the event occurs

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.

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.

Open API documentation ↗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"
}

In practice