Get started #

Our RCS API allows you to connect your web services and applications to mobile operators worldwide and is designed to handle high volumes of RCS traffic, making it perfectly suited for large-scale conversations, chatbots, OTPs, and marketing with Rich Content and product carousels, among other uses.


Create an account #

To get started, you first and foremost need an account, which you can skapa här.

Once you have created your account, log in to our user portal to access your credentials, which are described in more detail in the step below.


API Endpoint #

The base URL for endpoints according to the API reference in our RESTful API is: https://api.ip1.net/v3/

All requests must be made over HTTPS.

The system has a limit of 30 requests/sec per account.


All our API endpoints are protected by authentication via HTTP Bearer tokens, which we provide. Each account you create can have multiple keys with different restrictions on allowed IP addresses that you specify yourself. You manage the API keys in our user portal.

Logga in i användarportalen med din iP.1-användare som skapades i samband med din kontoregistrering.

  1. Gå till ”Konton”.
  2. Gå till ”Behörigheter”
  3. Gå till ”API-nycklar”
  4. Klicka på ”Lägg till ny nyckel”,
  5. Ange ett namn och eventuella IP-begränsningar
  6. Klicka på ”Lägg till”.

Pagination #

All endpoints under /v3/ returns a collection of documents (Conversations, messages, etc.) has pagination enabled. We are using database-style pagination with Start, limit oh order as parameter name.Startlimit oh orderis a way to 0, 50 oh ASC in that order, but you can change them by specifying them as query parameters when making an HTTP call like this:

?start=0&limit=200&order=DESC

Link head #

You will also receive a link header containing pagination information.

📋
Länkhuvud
Copy to clipboard
Link: ; rel="next",
      ; rel="last"

This example includes line breaks for readability.

Possible values for road is the following:

Name Description of the project
self The link relationship for the requested results page.
First The link relation for the first results page.
previous The link relationship for the immediately preceding result page
next Link relation for the immediately next results page.
last The link relationship for the last results page.