Produktionsklar mobil infrastrukturHTTPS API · Android & iOS · Dokumenterad slutänd för att avslutaUtforska plattformen
PLATFORMAPI-första arkitekturSäker enhet parningLeverans synlighetMulti-device kontrollVersioned dokumentation
Utvecklare hub/Ring API

CALL · 3 documented operations

Call API documentation

Retrieve missed, incoming answered and outgoing calls synchronized by connected mobile devices.

A connected smartphone managing calls and live analytics
REST base URLhttps://api.smsmobileapi.com

JSON responses · HTTPS required · UTF-8

Connect your API key

Connect once, then test endpoints across SMS, calls, notifications, WhatsApp and email.

Börja här

Your first request in four steps

1

Connect a phone and enable call synchronization.

2

Copy the API key from the dashboard.

3

Call the missed or incoming list endpoint.

4

Paginate with limit and offset and store timestamps in UTC.

The secure SMSMobileAPI mobile app connecting a phone to the web dashboard and REST API for SMS and call operations
Encrypted mobile-to-platform connection

Official mobile application

The secure bridge between your phone, dashboard and API.

SMS and call operations pass through the official SMSMobileAPI app installed on your connected phone. The app securely pairs the device with your account, synchronizes authorized events and links the mobile network to the dashboard and REST API.

1Mobile appPairs the phone and its SIM 2Encrypted linkAuthenticates and protects data in transit 3Dashboard & APIControls workflows and activity
  • Signed releases distributed through the official Google Play and Apple App Store listings
  • Google and Apple platform review, signing and distribution controls
  • Secure device pairing, HTTPS transport and authenticated API access
  • Only the permissions required for the mobile features you enable
Get the official SMSMobileAPI app on Google Play Download the official SMSMobileAPI app on the Apple App Store
Capabilities depend on the permissions and background access allowed by Android or iOS.

Autentisering

Keep credentials on your server

Call endpoints use the apikey query parameter. The API validates both the key and the active subscription before returning call activity.

Before you integrate
  • Background operating-system restrictions can delay mobile call synchronization by several minutes. Open the app to request a manual synchronization when testing.

List missed calls

#
ENDPOINThttps://api.smsmobileapi.com/call/missed/list/

Returns missed calls from newest to oldest.

When to use it

Use it to trigger callback workflows and missed-call alerts.

Parametrar

NameTypeRequirementBeskrivning
apikey string Nödvändig Din API-nyckel.
offset integer Optional Pagination offset; default 0.
limit integer Optional Rows per request; default 100, maximum 500.
search string Optional Search caller number or cached name.
date_start YYYY-MM-DD Optional Include calls from 00:00:00 on this day.
date_end YYYY-MM-DD Optional Include calls until 23:59:59 on this day.

Request example

ringla
curl "https://api.smsmobileapi.com/call/missed/list/?apikey=YOUR_API_KEY&offset=0&limit=100"

Example response

JSON
{
  "success": true,
  "offset": 0,
  "limit": 100,
  "count": 1,
  "data": [{"number": "+15551230001", "name": "Alex Carter", "date": "2026-03-20 16:12:28"}]
}

Want to run this request? Connect your API key at the top of the page to unlock the interactive tester.

Connect key ↑

List incoming answered calls

#
ENDPOINThttps://api.smsmobileapi.com/call/incoming/list/

Returns answered incoming calls with duration, timestamps and cached contact details.

When to use it

Use it for call reporting, CRM history and customer-service metrics.

Parametrar

NameTypeRequirementBeskrivning
apikey string Nödvändig Din API-nyckel.
limit integer Optional Default 50, maximum 200.
offset integer Optional Pagination offset.
sort_by enum Optional call_date_ms, call_datetime_utc, duration_sec, phone_number, created_at, cached_name or geo_location.
sort_dir asc | desc Optional Default desc.
date_from_ms Unix milliseconds Optional Minimum call timestamp.
date_to_ms Unix milliseconds Optional Maximum call timestamp.
q string Optional Search phone number or cached name.

Request example

ringla
curl "https://api.smsmobileapi.com/call/incoming/list/?apikey=YOUR_API_KEY&limit=50&sort_by=call_date_ms&sort_dir=desc"

Example response

JSON
{
  "success": true,
  "count": 1,
  "rows": [{
    "phone_number": "+15551230010",
    "cached_name": "Jordan Blake",
    "call_date_ms": 1774027779390,
    "call_datetime_utc": "2026-03-20 17:29:39",
    "duration_sec": 23,
    "geo_location": "Canada"
  }]
}

Want to run this request? Connect your API key at the top of the page to unlock the interactive tester.

Connect key ↑

List outgoing calls

#
ENDPOINThttps://api.smsmobileapi.com/call/outgoing/list/

Returns calls placed from connected devices.

When to use it

Use it to complete call timelines and analyze outbound activity.

Parametrar

NameTypeRequirementBeskrivning
apikey string Nödvändig Din API-nyckel.
limit integer Optional Default 50, maximum 200.
offset integer Optional Pagination offset.
sort_by enum Optional call_date_ms, call_datetime_utc, duration_sec, phone_number, created_at, cached_name or geo_location.
sort_dir asc | desc Optional Default desc.
date_from_ms Unix milliseconds Optional Minimum call timestamp.
date_to_ms Unix milliseconds Optional Maximum call timestamp.
q string Optional Search phone number or cached name.

Request example

ringla
curl "https://api.smsmobileapi.com/call/outgoing/list/?apikey=YOUR_API_KEY&limit=50&offset=0&sort_by=call_date_ms&sort_dir=desc"

Example response

JSON
{
  "success": true,
  "count": 1,
  "rows": [{
    "phone_number": "+15551230020",
    "cached_name": "Casey Morgan",
    "call_date_ms": 1774025965645,
    "call_datetime_utc": "2026-03-20 16:59:25",
    "duration_sec": 61,
    "geo_location": "Canada"
  }]
}

Want to run this request? Connect your API key at the top of the page to unlock the interactive tester.

Connect key ↑

Felsökning

Errors and safe retries

Read the HTTP status and the JSON error field before retrying. Do not retry validation or authentication failures without correcting the request first.

HTTPKodkodWhat to do
400missing_apikeyThe apikey parameter is missing or empty.
403invalid_apikeyThe key is not recognized.
403api_expiredThe subscription linked to the key has expired.
500server_errorThe request could not be completed by the call service.
Retry ruleRetry only transient 429 and 5xx responses. Start after 1 second, then back off to 2, 4 and 8 seconds.

Need help?

Bring the request context—not your secrets.

Share the endpoint, timestamp, HTTP status and sanitized response. Never include API keys, tokens or private message content.

Contact API support →