Rate this page:

Thanks for rating this page!

We are always striving to improve our documentation quality, and your feedback is valuable to us. How could this documentation serve you better?

Sync via MQTT: Overview

Sync for IoT is currently in Developer Preview, which means access is by invite only. If you'd like to try what you see in these docs, sign up for the developer preview and the team at Twilio will get you onboarded as soon as possible.

Within the Internet of Things, MQTT has emerged as the de-facto standard protocol for low-power, low-footprint devices. The protocol supports this domain with extraordinarily low network overhead and a good model for direct connectivity and connectivity through a gateway. In addition, open-source MQTT clients are available for virtually every platform.

In Twilio, we use the MQTT protocol to represent Sync state to low-power devices. This means your IoT device state is available to your backend services (via web hooks) and to your browser or mobile device, as well as the reverse direction. To support this, we at Twilio have applied a convention to the MQTT topic hierarchy, and we have interpreted particular MQTT protocol features (e.g. “clean sessions”, quality-of-service) through the lens of state synchronization.

Twilio for Deployed Devices - Using MQTT Gateway

In this section, you can find information about:

If you haven’t yet, head over to our Quickstart library to get a working MQTT program with which to experiment.

Rate this page:

Need some help?

We all do sometimes; code is hard. Get help now from our support team, or lean on the wisdom of the crowd browsing the Twilio tag on Stack Overflow.