inMobile REST API
communication:inmobile · inmobile.com ↗
# Introduction This document is a technical description of our REST API used for external systems to send sms messages and to retrieve a status for each sms message sent and to maintain lists and blacklists. In order…
About the inMobile REST API API
inMobile REST API API on Apizie: 36 endpoints (Returns all blacklists (Paged result. Follow _links.next to fetch all), Create an entry in blacklist, Get entry by id, Delete entry by id, …) returned as clean JSON through one API key. Send your own provider key in the x-upstream-key header. Call it over REST at https://apizie.tech/v1/communication:inmobile/{endpoint} or from Claude, ChatGPT and Cursor through the Apizie MCP server. Free plan: 1,000 requests a month.
| Project key | communication:inmobile |
|---|---|
| Status | Your key |
| Endpoints | 36 |
| Category | Communication |
| Source | inmobile.com |
| Base URL | https://apizie.tech/v1/communication:inmobile/{endpoint} |
| For AI tools | OpenAPI spec · Markdown (what is this?) |
inMobile REST API API FAQ
How do I call the inMobile REST API API?
Create a free Apizie key, then send GET https://apizie.tech/v1/communication:inmobile/blacklist-get-all with the header x-api-key. Every endpoint returns { project, data, timestamp }.
Is the inMobile REST API API free on Apizie?
Yes. The Free plan includes 1,000 requests a month at 100 requests a minute, no credit card. inMobile REST API itself also needs your own key from api.inmobile.com.
Can AI agents use the inMobile REST API API?
Yes. Add the Apizie MCP server (https://apizie.tech/mcp) to Claude, ChatGPT, Cursor or VS Code, then ask in plain language. The agent calls run_scraper with project key communication:inmobile.
What is the status of the inMobile REST API API?
Needs your own provider key (bring your own key)