Webcom Mobi API Docs
RU
  • Introduction
  • СПОСОБЫ ВЗАИМОДЕЙСТВИЯ С A2P ПЛАТФОРМОЙ
    • JSON specification
      • Sending SMS, Viber, Flash SMS, WAP-Push
      • SMS status request
        • POST request
        • Webhook
      • Balance check request
    • HTTP GET specification
      • Sending SMS
      • Sending Viber
      • Sending Cascade
      • Request message status
      • Registration
    • XML specification
      • Sending SMS, Viber, Flash SMS, WAP-Push
      • SMS status request
        • POST request
        • Webhook
      • Balance check request
      • Request to receive a list of senders
      • Request to add senders
      • Request for incoming SMS
      • Request for information by phone number
      • Request for obtaining the list of bases
      • Request to change parameters, add/remove bases
      • Request for receiving the list of subscribers of the base
      • Request to add/edit/delete subscribers of the base
      • Request to get the list of numbers from the STOP list
      • Request to add/remove subscribers to the STOP list
      • Request to receive the list of scheduled SMS
      • Request to delete a scheduled SMS
      • Request to get the time of change of something
      • Request for time verification
      • File upload request
      • Request to refill users' balance
    • ВЗАИМОДЕЙСТВИЕ С ПЛАТФОРМОЙ MSG (НЕОФ КАНАЛЫ)
    • Specification JSON
      • Чекинг базы номеров
Powered by GitBook
On this page
  • Parameter decoding
  • Returned client server response in JSON document
  1. СПОСОБЫ ВЗАИМОДЕЙСТВИЯ С A2P ПЛАТФОРМОЙ
  2. JSON specification
  3. SMS status request

Webhook

It is necessary to tell the manager the address of your server, which will receive SMS statuses

A method for sending a JSON document: POST

For example, in php, a JSON document would be accessed via the function file_get_contents("php://input") or a variable $GLOBALS['HTTP_RAW_POST_DATA']

The system sends a JSON document to the client server with the following content:

[
    {
        "id_sms": "SMS ID in the system to check the status",
        "time": "2011-01-01 12:57:46",
        "state": "Status"
        },
    {
        "id_sms": "SMS ID in the system to check the status",
        "time": "2011-01-01 12:57:46",
        "state": "Status"
    }
]

Parameter decoding

Parameter
Data type
Description

id_sms

Int

SMS message number received in the response JSON-document in the process of sending SMS message

time

String

Time of status change

state

String

Last message status:

  • "send" - message status not received. In this case, an empty time (time="") is transmitted

  • "not_deliver" - the message was not delivered. Final status (does not change with time)

  • "expired" - the subscriber was not in the network at the moments when the delivery attempt was made. Final status (does not change with time)

  • "deliver" - the message has been delivered.

  • "read" - the message has been read. Final status (does not change over time)

  • "partly_deliver" - the message was sent, but the status was not receive

Returned client server response in JSON document

If the client server does not transmit id_sms, the status will be considered as not received by the client. In this case 5 attempts will be made to deliver the status.

[
    {
        "id_sms":3234
    },
    {
        "id_sms":3235
    }
]

Last updated 1 year ago