Blog

You asked, we listened.

Our developer community had told us that they would like greater transparency and simple indicators to determine if TelstraDev services are functioning as expected. We are excited to announce just that, with the launch of TelstraDev’s status page: https://status.dev.telstra.com/

Last year we were proud to announce our partnership with Arduino to help create an (read more about it here https://exchange.telstra.com.au/our-exclusive-partnership-with-arduino-set-to-fuel-the-growth-of-iot-in-australia/), IoT network ready, device for developers. For us this partnership is really important to help create an IoT network specific device that is quick and easy to use, while being versatile to prototype with and has a wealth of library support.

One area that we have recently tuned is our Messaging API, more specifically MMS performance. The goal was to measure the throughputs we could support through the API and to iteratively re-engineer our server-side functions to increase our capacity to meet our customer's needs.

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.

Hello, my name is Steven Cooper, also known as DeveloperSteve, and I am the new API and Platform Evangelist at Telstra. After recently coming from being a CTO at a start-up and running developer relations at PayPal and Xero, I know the importance of having the right tools and resources in place for developers. This is why it’s so exciting to be building a developer community at an iconic company, Telstra, which touches on so many people throughout Australia and also the world.