In this blog, I'll showcase some of the interesting things you can do with the Internet of Things (IoT) and Azure services at home, that could potentially be commercialised in an industrialised environment.
You are here
In this blog series, I'll explan how I used the Internet of Things (IoT) to enable my gate, garage door and garden irrigation system using Azure IoT Hub, ESP32, IFTTT, .Net Core and much more.
Have you ever wondered what an API is and why you should care?
Have you ever had a mid-career crisis and considered going back to uni for a computer science degree because coding is the future?
Have you heard me talk about the Messaging API and want to try it yourself?
Then you've come to the right place!
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.
Welcome to the second in a two part series on understanding the messaging API callbacks. In our first post we covered using postman and setting up to handle the message callback. If you haven’t yet read the first post you can check that out at Understanding Messaging API Callbacks - Part 1.
The callback functionality of the messaging API is a great utility allowing you to track the delivery status of sent messages, and receive replies to your dedicated phone number without the need of making additional API calls.
In this first of 2-post series, I will walk through how to set up callbacks for your app and how to develop and test callback features without having a hosted endpoint.