(function(i,s,o,g,r,a,m){i['GoogleAnalyticsObject']=r;i[r]=i[r]||function(){ (i[r].q=i[r].q||[]).push(arguments)},i[r].l=1*new Date();a=s.createElement(o), m=s.getElementsByTagName(o)[0];a.async=1;a.data-privacy-src=g;m.parentNode.insertBefore(a,m) })(window,document,'script','https://www.google-analytics.com/analytics.js','ga'); ga('create', 'UA-3079425-7', 'auto'); ga('send', 'pageview');

Message Inbox Postbacks

Table of Contents

SMS/MMS MO Postbacks

The MMS MO / SMS MO Postback API notifies you that a customer has replied to your message, or interacted to one of your keywords. To receive SMS MO postback notifications you need to have that option enabled in your account API. You can setup a separate Postback URL specifically for SMS/MMS MO’s.

SMS MO Information:

Once enabled you will receive an notification immediately when someone interacts with your shared shortcode campaign or your dedicated shortcode. Each message comes back in its own postback notification.

MMS MO Information:

To receive MMS MO postback you need to configure it within the particular MMS Inbox keyword campaign. Once the MMS MO postback is enabled in the MMS Inbox campaign you will start receiving postbacks for each MMS MO received on the MMS MO Keyword or replies to an SMS sent. If you have opted to enable the MMS MO moderation panel, then the postback notifications will only be sent upon approval by the moderator.

SMS MO

This postback notifies you when an SMS MO is received.

VariableDescription
CODEN211.
ORIGINSMS_MO.
FROMSMS senders mobile number.
TOShortcode or longcode the SMS was sent to.
TEXTThe actual text that was sent by the sender.
RECEIVEDTimestamp of the SMS received by our server.
TRANSACTIONIDTransactionId for the SMS MO transaction that occurred.
<POSTBACK>
    <ORIGIN>SMS_MO</ORIGIN>
    <CODE>N211</CODE>
    <FROM>15552312102</FROM>
    <TO>86717</TO>
    <TEXT>STOP</TEXT>
    <RECEIVED>2011-09-28T17:31:02-04:00</RECEIVED>
    <TRANSACTIONID>511XG-02294-192SA-482H8</TRANSACTIONID>
</POSTBACK>

MMS MO

This postback notifies you when an MMS MO is received.

VariableDescription
CODEN401.
ORIGINMMS_MO.
FROMThe phone number, including the country code, of the sender.
TOThe recipient shortcode or longcode.
KEYWORDIf a keyword was recognized in the first word of the subject or the first word body of the message and it matched to a MMS Inbox Keyword campaign that keyword will be passed in this node.
SUBJECTThe subject field of the MMS if it exists. Subjects are optional
TRACKINGIDA tracking ID, skycore has assigned this message.
SPIDThe SPID of the sender’s carrier.
TIMESTAMPThe timestamp that our system received the MMS MO.
CONTENTContains the file nodes sent in the MMS MO.
FILEA series of sub-nodes that contains a single URL to a picture, video, audio or text file sent in the MMS MO within each node. The URL points to the location of the content on our servers. For those developing the back-end handling of the postback URL, you may choose to download/store these content files for whatever purpose you see fit. You may also choose to store the URLs for download at a future time. The file will be removed based on the terms of your contract.
<POSTBACK>
    <ORIGIN>MMS_MO</ORIGIN>
    <CODE>N401</CODE>
    <FROM>13217949521</FROM>
    <TO>74700</TO>
    <KEYWORD>all</KEYWORD>
    <SUBJECT>Hello there</SUBJECT> 
    <TRACKINGID>MMS_MO_iLnCRrL6</TRACKINGID>
    <SPID>0001470</SPID>
    <TIMESTAMP>2014-02-03T11:19:49-05:00</TIMESTAMP>
    <CONTENT>
        <FILE>URL of Content Here</FILE>
        <FILE>URL of Content Here</FILE>
        <FILE>URL of Content Here</FILE>
    </CONTENT>
</POSTBACK>
We use cookies for navigation, chat, analytics and forms. Will you accept cookies to access the full functionality of this site? Privacy Policy Accept
Go to Top