inMobile REST API
39
AI ReadinessNon-Ready (F)39/100
Agent-ready OpenAPI document · curated by JenticCommunicationsSms Messagingbasic,apiKey36 EndpointsREST
Know of an official OpenAPI document? Contribute it →
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.
Use for: I want to send an SMS notification to a customer, Send a templated email to a list of recipients, Add a phone number to the SMS blacklist, Retrieve all incoming SMS replies from yesterday
Not supported: Does not handle voice calls, video, or push notifications - use for SMS, MMS, templated email, list/blacklist management, and GDPR deletion requests only.
Jentic publishes the only available OpenAPI specification for inMobile REST API, keeping it validated and agent-ready. inMobile is a Danish messaging gateway that sends transactional and marketing SMS, MMS, and email on behalf of European businesses, with strong list-management and GDPR features. The version 4 REST API spans 36 endpoints across SMS outgoing/incoming, email outgoing with templates, recipient lists, blacklists, GDPR information-deletion requests, and operator tools. Authentication is HTTP Basic or an apikey query parameter.
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.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Finmobile.com%2Finmobile" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Finmobile.com%2Finmobile" | sh
jentic register # connects your agent to your Jentic One instanceJentic 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
Maintain SMS blacklists by ID or phone number under /v4/blacklist and /v4/blacklist/ByNumber
Retrieve SMS-incoming events and email events for delivery tracking and reply handling
Manage email templates programmatically with the /v4/email/templates endpoints
Submit GDPR information-deletion requests via /v4/sms/gdpr/deletionrequests for EU compliance
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
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
Jentic AI Readiness Score
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
I
inMobile REST API
- Non-Ready (F)39/100
79
Foundational Compliance74
Developer Experience & Jentic Compatibility29
AI-Readiness & Agent Experience94
Agent Usability13
Security100
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
79
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: A-Signals: 4
97%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
100%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
21%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
74
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: A-Signals: 4
23%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
75%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
100%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
29
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: FSignals: 4
55%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
0%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
60%
Summary Coverage
Coverage of summaries across operations/tags/info.
94
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: A+Signals: 1
94%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
13
Security
Trust, risk posture, and security compliance.
Grade: FSignals: 1
12%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
100
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: A+Signals: 1
100%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the inMobile REST API by hand means choosing between HTTP Basic auth and an apikey query parameter, then mapping its SMS, email, and list endpoints yourself. Through Jentic you install once, import the inMobile REST API from the API Directory, store the credential once, and your agent calls it.
Permission scoping
inMobile takes the recipient and message content in the request body rather than the URL path, so limit the agent to the operations it needs, such as sending an SMS or adding a number to the blacklist. You choose which operations are allowed, so GDPR deletion requests are not included unless you add them.
Credential isolation
Your inMobile credential, whether the Basic auth value or the apikey, is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'send an SMS' or 'add a number to the blacklist', and Jentic returns the matching inMobile operation with its input schema so the agent calls the right endpoint without browsing the version 4 docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
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 with Jentic One, the self-hosted execution layer.
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 your Jentic One instance 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 with Jentic One, the self-hosted execution layer.
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.
Can I limit what my agent is allowed to do with the inMobile REST API?
Yes. Because you run Jentic One yourself, your own rules decide which inMobile operations and credentials the agent can use, so you can allow only what it needs, such as sending an SMS via /v4/sms/outgoing or adding a number to the blacklist via /v4/blacklist. Since inMobile takes the recipient and message content in the request body rather than the URL path, scoping happens at the operation level rather than by path pattern. Operations you do not grant, such as GDPR deletion requests via /v4/sms/gdpr/deletionrequests, stay out of the agent's reach unless you explicitly add them.
GET STARTED