Facebookpixel Document API for Notification - SMSMobileAPI
SMSMobileAPI – Notification API Documentation

Quickstart

Base URL

GET https://api.smsmobileapi.com
All examples below are shown as GET requests for simplicity. The notification/send endpoint also accepts POST and JSON body. Replace YOUR_API_KEY with your real key.

Examples

GET https://api.smsmobileapi.com/notification/send?apikey=YOUR_API_KEY&sid=TARGET_SIDENTIFIANT&title=Notification&message=Hello%20world&type=notification
GET https://api.smsmobileapi.com/notification/list/?apikey=YOUR_API_KEY
GET https://api.smsmobileapi.com/notification/list/?apikey=YOUR_API_KEY&sidentifiant=TARGET_SIDENTIFIANT&distribued=1&date_from=2026-03-01&date_to=2026-03-18

Authentication

Notification endpoints authenticate using the apikey parameter.

Required on both endpoints: the API key is mandatory for notification/send and notification/list.

Common concepts

Target mobile

Notifications are sent to a specific mobile device using sid. The list endpoint can filter the same target using sidentifiant or sid.

Distributed status

  • distribued=1 means the notification was distributed.
  • distribued=0 means not distributed.
  • distribued_status returns distributed or not_distributed.

Dates and timezones

  • sent_* fields represent the notification send date/time in GMT.
  • distributed_* fields represent the distribution date/time in GMT.
  • *_at_unix fields are Unix timestamps.

List endpoint behavior

  • The list endpoint always returns a maximum of 200 rows.
  • Results are ordered from newest to oldest using send date/time.
  • Date filters use dateAjout internally and are exposed as date_from / date_to.

Errors

HTTP Example error Meaning
400 {"success":false,"message":"Missing required param: apikey."} Missing or empty apikey.
400 {"success":false,"message":"Missing required params: apikey and sid are mandatory."} Missing sid on notification/send.
400 {"success":false,"message":"Missing required param: message."} Missing message on notification/send.
400 {"success":false,"message":"Invalid date_from format. Expected YYYY-MM-DD."} Invalid date_from format on notification/list.
400 {"success":false,"message":"Invalid distribued value. Allowed values: 0 or 1."} Invalid distribued filter value.
500 {"success":false,"message":"DB connection failed."} Database connection problem.
500 {"success":false,"message":"Query failed: ..."} SQL / execution error.

Notification – Send

Create a new notification for a target mobile device.

Endpoint

GET POST https://api.smsmobileapi.com/notification/send

Query / body parameters

ParameterTypeDescription
apikey string Required Your API key.
sid string Required Target mobile sidentifiant.
title string Optional Notification title. Default: Notification.
message string Required Notification message content.
type string Optional Notification type. Default: notification.

Example success response

{
  "success": true,
  "message": "Notification created.",
  "id": 22087,
  "apikey": "YOUR_API_KEY",
  "sid": "508b004b4aadacc4"
}

Notification – List

Retrieve the latest notifications for an API key, with optional filtering.

Endpoint

GET https://api.smsmobileapi.com/notification/list/

Query parameters

ParameterTypeDescription
apikey string Required Your API key.
sidentifiant string Optional Filter notifications by target mobile.
sid string Optional Alias of sidentifiant.
distribued 0 | 1 Optional 1 = distributed only, 0 = not distributed only.
date_from YYYY-MM-DD Optional Filter sent date from this day.
date_to YYYY-MM-DD Optional Filter sent date up to this day.
The list endpoint returns at most 200 rows and orders them by newest sent notification first.

Example success response

{
  "success": true,
  "message": "Notifications retrieved successfully.",
  "filters": {
    "sidentifiant": "508b004b4aadacc4",
    "distribued": "1",
    "date_from": "",
    "date_to": "",
    "limit": 200
  },
  "count": 1,
  "data": [
    {
      "sidentifiant": "508b004b4aadacc4",
      "title": "Notification",
      "message": "vers miano",
      "distribued": "1",
      "distribued_status": "distributed",
      "distributed_date_gmt": "2026-03-18",
      "distributed_time_gmt": "10:18:30",
      "distributed_at_gmt": "2026-03-18 10:18:30",
      "distributed_at_unix": 1773829110,
      "distributed_timezone": "GMT",
      "sent_date_gmt": "2026-03-18",
      "sent_time_gmt": "10:15:03",
      "sent_at_gmt": "2026-03-18 10:15:03",
      "sent_at_unix": 1773828903,
      "sent_timezone": "GMT"
    }
  ]
}

Send response fields

FieldTypeDescription
successboolRequest status.
messagestringHuman-readable result message.
idintCreated notification ID in database.
apikeystringEchoed API key.
sidstringTarget mobile sidentifiant used during creation.

List response fields

FieldTypeDescription
successboolRequest status.
messagestringHuman-readable result message.
filtersobjectEchoed filters used by the request.
countintNumber of returned notifications.
dataarrayList of notifications.
data[].sidentifiantstringTarget mobile identifier.
data[].titlestringNotification title.
data[].messagestringNotification message.
data[].distribuedstringRaw distributed flag.
data[].distribued_statusstringdistributed or not_distributed.
data[].distributed_date_gmtstringDistribution date in GMT.
data[].distributed_time_gmtstringDistribution time in GMT.
data[].distributed_at_gmtstringFull distribution datetime in GMT.
data[].distributed_at_unixint|nullDistribution datetime as Unix timestamp.
data[].distributed_timezonestringAlways GMT.
data[].sent_date_gmtstringSend date in GMT.
data[].sent_time_gmtstringSend time in GMT.
data[].sent_at_gmtstringFull send datetime in GMT.
data[].sent_at_unixint|nullSend datetime as Unix timestamp.
data[].sent_timezonestringAlways GMT.
💬 Live Chat
💬 Live Chat Available
Have any questions or need assistance ?
Our team is here to help you!

Enter your email address
to help us follow up on your request :
Dashboard