Receive MO SMS

The system can dispatch MO-SMS from endpoints towards a configurable URL, in this case the EMnify System will act as a HTTP client and you will need to provide a HTTP server to accept the request. Please see Service Profile Configuration on how to set up an API Callback URL.

Your server needs to respond with HTTP Code 2XX to accept the request.

EMnify will optionally send a JWT to your server based on a secret configured in the corresponding service profile. By verifying the JWT, your server can ensure the request is actually coming from EMnify.

Please see https://jwt.io for libraries that work with JWTs.

A2P / P2P

Our system distinguishes A2P SMS (application-to-person) from P2P SMS (person-to-person) based on the length of the source (MO SMS) or the destination (MT SMS) address.

  • If there are 8 digits or less (i.e. an invalid MSISDN), an SMS will be considered A2P.
  • If there are 9 digits or more, an SMS will be processed as MSISDN and will be considered P2P.

To dispatch SMS MO to your application (A2P) and at the same time have P2P SMS enabled, the destination number (dest_address) must be limited to 8 digits or less.

{
  "id": 123,
  "endpoint": {
    "id": 1,
    "name": "Your Endpoint"
  },
  "organisation": {
    "id": 4,
    "name": "Your Organisation Name"
  },
  "source_address": 432311234,
  "dest_address": 12345678,
  "payload": "This is the message text",
  "dcs": 0,
  "pid": 0,
  "submit_date": {}
}