For the complete documentation index, see llms.txt. This page is also available as Markdown.

Callbacks and inbound SMS

Handle replies, delivery notifications, and inbound SMS forwarding.

SMS reply callback

Use the Answer function to receive SMS replies.

Parameter
Type
Description

AddressTo

Required

Recipient number

AddressFrom

Required

Sender number

Message

Required

Reply content

TimeStamp

Required

Receipt time in dd.mm.yyyy hh:mm:ss format

JobID

Optional

Original message identifier

Acknowledge the callback with HTTP 200 OK.

Example:

http://www.mycompany.com/answers?Function=Answer&AddressTo=0041766012999&AddressFrom=0041791234567&Message=My+reply&TimeStamp=11%2E12%2E2015+10%3A37%3A00

Delivery notification callback

Use the Notification function to receive delivery notifications.

Parameter
Type
Description

ResultCode

Required

Message status code

ResultText

Required

Message status text

Number

Required

Recipient number

TimeStamp

Required

Message receipt time in dd.mm.yyyy hh:mm:ss format

JobID

Optional

Original message identifier

Acknowledge the callback with HTTP 200 OK.

Example:

Notification result codes

ResultCode
ResultText
Description

0

Message has been delivered

Delivery confirmed by the recipient

1

Message has been buffered

Delivery could not yet be confirmed

2

Message has not been delivered

Delivery could not be confirmed

3

Error Code / Error Message

Error while handing off to the destination center

4

Transmission OK

Job was forwarded to the destination center

Inbound SMS forwarding

Incoming SMS can be forwarded to an HTTP or HTTPS URL.

Configure the target URL per leased SMS number in the portal.

GET forwarding

eCall appends these parameters to the configured URL:

Parameter
Description

Function

Always IncomingSMS

AddressTo

eCall receive number

AddressFrom

Sender number

Message

SMS content

TimeStamp

Receipt time in DD.MM.YYYY HH:MM:SS format

Example:

Decoded values:

Parameter
Value

Function

IncomingSMS

AddressTo

0041766666666

AddressFrom

0041799999999

Message

Yes, noon is ok.

TimeStamp

01.01.2020 12:00:00

POST forwarding

POST forwarding sends JSON.

Field
Description

messageId

GUID that uniquely identifies the message

channel

Always Sms

to

eCall receive number

from

Sender number

content.type

Always Text

content.text

SMS content

timestamp

Receipt time in UTC using ISO 8601

Example:

Last updated

Was this helpful?