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 an XML document
  1. СПОСОБЫ ВЗАИМОДЕЙСТВИЯ С A2P ПЛАТФОРМОЙ
  2. XML specification
  3. SMS status request

Webhook

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

Method of sending XML document: POST

For example, in phpXML, the document will be accessible via a variable$GLOBALS['HTTP_RAW_POST_DATA']

The system sends an XML document to the client server with the following content:

<?xml version="1.0" encoding="utf-8" ?>
<response>.
     <state id_sms="IDSMS in system to check status" time="2011-01-01 12:57:46" sms="Status">Status</state>
     <state id_sms="IDSMS in system to check status" time="2011-01-01 12:57:46" sms="Status" viber="Status">Status</state>
     <state id_sms="IDSMS in system to check status" time="2011-01-01 12:57:46" viber="Status">Status</state>
</response>

Parameter decoding

Parameter
Data type
Description

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 received.

state.id_sms

Int

SMS message number received in the response XML document in the process of sending SMS message

state.time

String

Time of status change

state.sms, state.viber

String

Message status.

The name of the field depends on the type of the message to be sent and resent

Returned client server response in an XML 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.

<?xml version="1.0" encoding="utf-8" ?>
<response>
     <id_sms>3234</id_sms>
     <id_sms>3235</id_sms>
</response>

Last updated 1 year ago