Send SMS
Deliver transactional alerts, OTP codes, appointment reminders, and conversational prompts to any supported destination. Use /send for live traffic or /simulate to test flows without billing.
Automation
AI Agents welcome
Simmcomm encourages AI agents, LLM toolchains, and workflow orchestrators to use our REST API for reliable, programmable mobile messaging.
Whether you are building an autonomous support agent, a compliance notifier, or a multi-step onboarding flow, our HTTPS API gives agents structured access to SMS delivery, HLR lookups, carrier data, and inbound message notifications — without proprietary SDKs or manual integration work.
Point your agent or orchestration platform at our OpenAPI specification and start automating.
What agents can automate
Common tasks map directly to documented API operations. Agents can chain these calls inside larger workflows — validating a number before sending, waiting for a delivery receipt, or reacting to an inbound reply.
HLR lookup
Resolve whether an MSISDN is reachable, which network it is on, and whether it is ported — before you send. The /hlr endpoint supports synchronous responses and async webhook callbacks.
Inbound & status events
Subscribe to delivery receipts and mobile-originated (MO) messages via the notifications API or your own webhook URL, so agents can close the loop on two-way conversations.
Orchestration-ready
Our API is described with OpenAPI 3.1. Import the spec into your favourite agent framework or low-code automation tool — no custom connector required.
Dify
n8n
Make
Zapier
LangChain tools
Custom MCP servers
In platforms such as dify.ai and n8n.io, add Simmcomm as a custom OpenAPI tool or HTTP node. The schema defines request bodies, authentication, and response models so your agent knows exactly which parameters to pass.
Official OpenAPI specification — import this URL directly:
https://api.simmcomm.com/openapi.yaml Browse API documentationUse case: bi-directional chat bots
One of the most powerful patterns for AI agents is a true two-way SMS conversation — not just outbound blasts, but a channel where end users can reply and the agent continues the dialogue.
Automated customer care
An agent receives a support ticket or chat hand-off, looks up the customer's MSISDN via HLR to confirm reachability, then sends an opening SMS: "Hi Alex, this is Example Support. Reply to this message to continue with your case #4821."
When the customer texts back, the inbound MO message arrives at your webhook. The agent parses the reply, updates the ticket, and responds with the next step — escalating to a human only when needed.
1
Agent triggers HLR lookup on the customer's MSISDN
↓
2
Agent sends an outbound SMS via
/send
↓
3
Customer replies to your global reply number
↓
4
Simmcomm forwards the MO message to your webhook
↓
5
Agent processes the reply and sends the next SMS in the thread
Because replies are routed through a global reply SMS number, users do not need an app or a special short code — they simply respond to the message on their phone. Your agent maintains session context (ticket ID, language, escalation state) and keeps the conversation going until the task is complete.
Other agent workflows
Appointment confirmations — send a reminder, accept YES/NO/RESCHEDULE replies, and update the calendar automatically.
Field-service dispatch — notify a technician, receive status updates by SMS, and log outcomes back to your ERP.
Fraud & compliance alerts — validate the destination network with HLR, deliver a time-sensitive warning, and record delivery status for audit trails.
Get started
You will need API credentials from your Simmcomm account. Use /simulate to test agent workflows without sending live traffic or incurring charges.