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.

NOTE: This feature is currently only available to PAID apps.

 

 

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:

  • Is only available for PAID apps

  • 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

 

Feedback

If you have any questions or comments please do send those to telstradev@team.telstra.com. 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 https://dev.telstra.com.

 

Related Blogs

anonymous's picture

By Michelle Howie

15/7/21

  • arduino
  • iot

Real Time SMS alerts for dropped devices

  So in part 1 and part 2 of this workshop series, we’ve gone through how we can poll...
anonymous's picture

By Michelle Howie

15/7/21

  • arduino
  • iot

Ask for Environmental Sensor Data via SMS

If you have an environmental sensor set up in your home, office, farm etc and want to check the temp...
anonymous's picture

By Michelle Howie

15/7/21

  • arduino
  • iot

Control your IoT Device remotely with SMS commands

Developing with the Internet of Things is fun. It’s challenging. It’s frustrating at tim...
anonymous's picture

By Tim McMahon

2/6/21

  • messagingAPI
  • airquality

SMS alerts for hazardous air quality during bushfire season

I woke up one morning in January 2020 and discovered that the air quality in Melbourne had drop...
iot home garden project with arduino and azure
anonymous's picture

By keith coutlemanis

10/11/20

  • arduino
  • azure

Azure Internet of Things Garden Project with Arduino

I want to showcase a project I have been working on to reflect the interesting things you can do wit...
anonymous's picture

By Trent Steenholdt

10/11/20

  • iot
  • DIY

Home IoT Project using Azure

In this blog series, I’m going to write about how Internet of Things (IoT) enabled my gate,...
anonymous's picture

By Michelle Howie

20/10/20

  • hackathon
  • messagingAPI

Connecting our community in an emergency with mobile...

What do you get when you give 700 Hackers, Hustlers and Hipsters across Australia and New Zealand, a...
anonymous's picture

By Michelle Howie

3/8/20

  • 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

30/8/18

  • 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

12/2/18

  • 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

30/1/18

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