inMobile REST API

Name: inMobile REST API
Brand: inMobile REST API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentCommunicationsSms Messagingbasic,apiKey36 EndpointsREST

For Agents

Send SMS, MMS, and templated email messages, manage recipient lists and blacklists, retrieve email and SMS events, and process GDPR deletion requests via the inMobile gateway.

Install Jentic One Beta

Connect the inMobile REST API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the inMobile REST API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with inMobile REST API.

Send transactional and marketing SMS messages individually or in batches via the SMS outgoing endpoints

Send templated and ad-hoc emails through /v4/email/outgoing and /v4/email/outgoing/sendusingtemplate

Manage subscriber lists for SMS campaigns under /v4/lists

GET STARTED

Start building with inMobile REST API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use inMobile REST API for, with concrete tasks.

★ Transactional SMS Notifications

Send order confirmations, delivery updates, and one-time passcodes over the inMobile SMS gateway. The SMS outgoing endpoints accept a recipient phone number, message body, and sender ID. Delivery events are exposed via the SMS incoming and event endpoints, so applications can mark messages as delivered or surface failures back to the user.

Send an SMS to +4520123456 with body 'Your package will arrive Tuesday between 9-12' from sender ID 'Acme'.

Templated Email Campaigns

Send templated emails (transactional or marketing) at scale by managing reusable templates via the /v4/email/templates endpoints and dispatching them with /v4/email/outgoing/sendusingtemplate. Useful for teams that want a single tool for SMS and email, particularly in Nordic markets where inMobile has strong operator relationships.

POST /v4/email/outgoing/sendusingtemplate with template ID 'welcome-001', recipient address, and merge variables for first_name.

GDPR-Compliant List Management

Maintain subscriber lists and blacklists in line with EU consent rules. /v4/lists handles segmentation; /v4/blacklist tracks opt-outs by ID or phone number; /v4/sms/gdpr/deletionrequests submits formal information-deletion requests when a user invokes their right to erasure. Built specifically for EU operators where GDPR breaches carry significant fines.

POST /v4/blacklist with a phone number to opt the user out, then POST /v4/sms/gdpr/deletionrequests to formally remove their data.

AI Agent for Customer Comms

An LLM agent handling customer support or proactive outreach uses inMobile to deliver SMS replies and email follow-ups. Through Jentic, the agent searches by intent ('send an SMS', 'send a templated email'), loads the schema, and executes — credentials and rate-limit handling are abstracted away. Ideal for Nordic-focused operations with EU residency requirements.

Send an SMS via /v4/sms/outgoing to a customer confirming a refund and follow up with a templated email through /v4/email/outgoing/sendusingtemplate.

Key Endpoints

36 endpoints — jentic publishes the only available openapi specification for inmobile rest api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/v4/email/outgoing

Send an ad-hoc email

POST

/v4/email/outgoing/sendusingtemplate

Send an email using a stored template

GET

/v4/email/outgoing/events

Retrieve email events for tracking

GET

/v4/blacklist

List all blacklist entries

POST

/v4/blacklist

Add a phone number to the blacklist

GET

/v4/lists

List subscriber lists

POST

/v4/lists

Create a new subscriber list

POST

/v4/sms/gdpr/deletionrequests

Create a GDPR information deletion request

POST

/v4/email/outgoing

Send an ad-hoc email

POST

/v4/email/outgoing/sendusingtemplate

Send an email using a stored template

GET

/v4/email/outgoing/events

Retrieve email events for tracking

GET

/v4/blacklist

List all blacklist entries

POST

/v4/blacklist

Add a phone number to the blacklist

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

inMobile credentials (HTTP Basic or apikey query parameter) are stored encrypted in the Jentic vault (MAXsystem). Agents call inMobile operations through scoped Jentic credentials and never hold the raw value, which is important for an API that can send paid SMS and email at volume.

Intent-based discovery

Agents search Jentic with intents like 'send an SMS' or 'add a number to the blacklist' and Jentic returns the matching inMobile operations with their input schemas, removing the need to read the version 4 docs.

Time to first call

Direct inMobile integration: a few hours to handle dual-auth and template/list shapes. Through Jentic: minutes — schema-first execution and credential vaulting handle the boilerplate.

FAQs

Specific to using inMobile REST API through Jentic.

Why is there no official OpenAPI spec for inMobile REST API?

inMobile does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call inMobile REST API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the inMobile REST API use?

The inMobile REST API supports HTTP Basic authentication and an 'apikey' query parameter as alternatives. Through Jentic, whichever credential you configure is stored encrypted in the MAXsystem vault and injected at runtime, so the agent never holds the raw key.

Can I send both SMS and email through the same API?

Yes. The /v4/sms/outgoing endpoints handle SMS and the /v4/email/outgoing endpoints handle email, including templated sends via /v4/email/outgoing/sendusingtemplate. Both share the same credentials and account context.

What are the rate limits for the inMobile REST API?

Rate limits are not encoded in the spec; they vary by account contract and operator routing in the Nordic markets inMobile primarily serves. Contact inMobile support to confirm the per-second send rate negotiated for your account.

How do I add a number to the blacklist through Jentic?

Search Jentic for 'add number to inMobile blacklist' to find POST /v4/blacklist (or DELETE /v4/blacklist/ByNumber to remove). Load the schema, supply the phone number, and execute. Get started at https://app.jentic.com/sign-up.

Does the API support GDPR deletion requests?

Yes. POST /v4/sms/gdpr/deletionrequests submits a formal information-deletion request for a phone number, which inMobile processes in line with its EU GDPR obligations. Use this when a user invokes their right to erasure.

inMobile REST API

Connect the inMobile REST API to your agent

Capabilities

Start building with inMobile REST API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs