Sorry, you need to enable JavaScript to visit this website.

You are here

Conversation via Telstra Messaging API

BY Christy Daguia 15 November 2018

Creating a message thread can be done via Telstra Messaging API, whereby you can continue sending and receiving messages to and from the same party as if it were a conversation. You can link the message you send with the replies that have come back for that message from a specific party. Central to this feature is the use of the replyRequest field when sending messages.


Prerequisite: A Provisioned Number


Make sure that you have a provisioned number. You can check this by using GET subscriptions.

If you do not have a provisioned number, you can use POST /provisioning/subscriptions.



In the example above, there is a notifyURL that has been specified during provisioning, thus any replies for the provisioned number will be sent back to the URL (i.e. messages sent to destinationAddress will be sent to the notifyURL)


Starting the Conversation


Send a message with replyRequest=true.

Note that replyRequest currently only works for one recipient. Also, replyRequest does not work with an alphanumeric from field.

In the example below, Telstra’s Messaging API will send back a ReplyAddress. You will notice that this number is different from your provisioned number.

Take note of the ReplyAddress as this can be re-used to continue the conversation with the other party. The thread will expire after seven days.



What the Other Party Receives


The recipient will receive the message in their device with the sender being the ReplyAddress. The recipient can then reply to the ReplyAddress.



Telstra Messaging API Reply Callbacks


Since there is a notifyURL specified in provisioning, this reply will be sent to the notifyURL.

If there was no notifyURL specified in provisioning, the reply can be retrieved using GET /messages.


To find out more about how the callbacks work, you can refer to the blog posts here and here.



Continue the Conversation

You can continue the conversation with this party by using the ReplyAddress from your first SEND message.

Make sure that you change the from field into the ReplyAddress number that was used.

This time, either omit the replyRequest field OR set replyRequest=false.

The other party will receive the new message as coming from the same ReplyAddress. The other party can then continue the conversation. And so forth.




Being able to create message threads is a very useful tool if you want to have a dedicated conversation with another party.


Just be mindful that this cool feature:

  • Requires you to set replyRequest=true in POST /messages

  • Currently only works for one recipient at a time (i.e. you cannot have an array of recipients in one POST /message)

  • Requires you to set from=ReplyAddress and omit replyRequest (or set replyRequest=false) for the subsequent POST /messages if you’d want to continue the thread

  • Telstra will be able to keep the thread alive for seven days



If you have any questions or comments please do send those to We can’t wait to see what you build with this feature. We would love to hear back from you on your experience of TelstraDev. You can also visit and register at


Related Blogs

iot home garden project with arduino and azure
anonymous's picture

By keith coutlemanis


  • arduino
  • azure

Azure IoT garden project with Arduino

In this blog, I'll showcase some of the interesting things you can do with the Internet of Thing...
anonymous's picture

By Trent Steenholdt


  • iot
  • azure

A home IoT project using Azure

In this blog series, I'll explan how I used the Internet of Things (IoT) to enable my gate, gara...
anonymous's picture

By Michelle Howie


  • messagingAPI
  • Tutorials

Get Started with the TelstraDev Messaging API

Have you ever wondered what an API is and why you should care? Have you ever had a mid-career cri...
anonymous's picture

By Rajeev Ramani


  • MMS
  • performance

Fine-tuning MMS performance on Telstra's Messaging API

  Here at TelstraDev, we strive to make the best possible developer experience, from the recen...
anonymous's picture

By Marcus Kennan


  • callbacks
  • Messaging SDK

Understanding Messaging API Callbacks - Part 2

Welcome to the second in a two part series on understanding the messaging API callbacks. In our firs...
anonymous's picture

By Marcus Kennan


  • callbacks
  • postman

Understanding Messaging API Callbacks - Part 1

The callback functionality of the messaging API is a great utility allowing you to track the deliver...