Replies arrive on the mobile number your contact already knows.
SMSMobileAPI / API
RECEIVED SMS API · YOUR MOBILE STAYS THE INBOX
Turn every SMS received on your mobile into usable application data.
Your contact sends a normal SMS to your existing mobile number. The message reaches your connected phone first, then SMSMobileAPI securely synchronizes the supported data so your application can retrieve, classify and process the reply.
No virtual receiving number replaces your phone: your mobile, SIM and existing number remain at the center of the exchange.
AA contact sends an SMS
“Can you call me back?”
+1 555 012 9841
Can you call me back?
/getsms/200sms.received
number+15550129841
deviceSales mobile
statusREADY
Your software uses it
Retrieve the sender, message, receiving mobile, timestamp, GUID and optional alias.
Centralize replies while preserving which connected phone received each SMS.
THE SIMPLE EXPLANATION
The API does not replace your phone. It makes its received SMS usable.
SMSMobileAPI adds a secure software layer around a real mobile inbox. This gives your CRM, support platform or internal application access to eligible received-message data without changing the number used by your contacts.
A contact sends an SMS
The contact writes to the real number attached to your SIM.
Your mobile receives it
The SMS arrives through your mobile operator on the connected phone.
The app synchronizes it
With the required permission and background access, the official app securely sends supported message data to your account.
Your software uses it
Retrieve it with the REST API, receive a Webhook V2 event or display it in a compatible integration.
A RESPONSE YOUR APPLICATION CAN USE
One request returns the message and the context needed to process it.
Use GET /getsms/ to list synchronized incoming SMS. Filter by receiving mobile, request only unread messages or retrieve messages after a Unix timestamp.
- number
- The sender in international format when available.
- message
- The SMS text synchronized from the connected mobile.
- sIdentifiantPhone
- The connected mobile that received the SMS.
- timestamp_unix
- The message time, ready for sorting and incremental synchronization.
- guid
- A stable message reference for read-state and follow-up operations.
- alias
- An optional contact or application label.
{
"result": {
"error": "",
"sms": [{
"sIdentifiantPhone": "508b004b4aadacc4",
"timestamp_unix": 1774041814,
"message": "Can you call me back?",
"number": "+15550129841",
"guid": "6BFD7DC7-3492-422D-8D02-4AF4E614F122",
"alias": "Alex Morgan"
}]
}
}CHOOSE THE RIGHT DELIVERY PATTERN
Pull messages by API—or react immediately with Webhook V2.
Both methods use the same connected mobile data. Choose according to how your application works, or combine them for fast reactions and reliable recovery.
Your application requests messages when it is ready.
- Build an inbox or scheduled synchronization
- Filter by mobile, time or unread state
- Recover messages after an interruption
SMSMobileAPI sends an sms.received event to your HTTPS destination.
- React without a polling loop
- Use durable delivery and automatic retries
- Start a workflow as soon as the event is available
MORE THAN A SIMPLE MESSAGE LIST
Build a complete received-SMS workflow.
/getsms/List received SMS
Use mobile, timestamp and unread filters to retrieve only what your application needs.
/getsms/set-read/Mark as processed
Update the SMSMobileAPI API read state after your application has handled a message.
/getsms/update/Attach an alias
Associate a contact name or application label with a received message.
/conversation/sms/list/Build conversations
Group incoming and outgoing messages by phone number for a support or CRM timeline.
Marking a message as read through the API does not change its read state inside the phone messaging application.
WHAT CAN YOU BUILD?
From one reply to a complete business process.
Create a shared SMS inbox
Route replies from several authorized phones into one support view while preserving the receiving mobile.
Complete the contact timeline
Add incoming replies to a customer record alongside outbound SMS and supported call activity.
Understand confirmations automatically
Detect confirmations, cancellations or rescheduling requests and update the next step.
Escalate important messages
Notify the right person, call an API or start a Workflow Studio automation when conditions match.
FROM ZERO TO THE FIRST API RESPONSE
Receive your first SMS through the API in four controlled steps.
- 1
Install and pair the mobile
Install the latest official SMSMobileAPI app and connect the compatible phone to your account.
- 2
Enable received-SMS access
In the mobile app, authorize received-SMS synchronization and the background operation required by your workflow.
- 3
Send a unique test message
Send an SMS from another number to the connected mobile and verify it in the received SMS dashboard log.
- 4
Call the endpoint securely
Keep the API key on your server, call /getsms/ and store the GUID so your application can avoid duplicate processing.
RECEIVED SMS API FAQ
Questions developers and operational teams ask first.
Does the API receive the SMS instead of my mobile?
No. Your compatible connected mobile and SIM receive the SMS first. SMSMobileAPI then synchronizes supported message data so it can be retrieved by your software.
Can several mobiles feed the same application?
Yes. Several authorized mobiles can be connected to one account, and the receiving mobile identifier lets your application preserve the source of each message.
Should I use polling or Webhook V2?
Use GET /getsms/ when your application controls the retrieval schedule or needs recovery. Use the sms.received Webhook V2 event when you want an HTTPS destination to react as soon as the event becomes available. Many production systems combine both.
How do I avoid processing the same message twice?
Store the message GUID in your application and make processing idempotent. After successful processing, you can also update the SMSMobileAPI API read state.
Does marking a message as read change the phone inbox?
No. The endpoint changes the API-side read state used by SMSMobileAPI workflows; it does not mark the message as read inside the phone messaging application.
Can I reply from my application?
Yes. Your application can call the SMS sending endpoint so a selected connected mobile sends the reply through its SIM and mobile number.
Let your software understand every useful reply received by your mobile.
Connect one phone, authorize received-SMS synchronization and test the complete journey before extending it to your CRM, support platform or automation.
