Help Center/ IoT Device Access/ User Guide/ Rules/ Data Forwarding to Third-Party Applications/ AMQP Data Forwarding/ Overview
Updated on 2024-11-06 GMT+08:00
View PDF
Share

Overview

The figure below shows the subscription and push process.

Push mechanism: After receiving a message from the platform, the application returns a response. (The automatic response mode is recommended.) If the application does not pull data after the connection is established, data will be stacked on the server. The server stores only the data that is received in the last 24 hours and occupies less than 1 GB disk space. If the application does not pull data in a timely manner, the platform clears expired and excess data on a rolling basis. If the application does not respond in time after receiving the message and the persistent connection is interrupted, the corresponding data will be pushed again in the next connection established.

Subscribing to Data

After connecting to IoTDA, an application calls an API to subscribe to data.

Format of Pushed Data

For details on the format of data pushed by the platform to applications after data subscription is created, see Data Transfer APIs.

In the HTTP message header, the value of Content-Type is application/json, and the character set is UTF-8.

APIs

Creating a Rule Action

Creating a Rule Trigger Condition

Modifying a Rule Trigger Condition

Data Transfer APIs

Creating an AMQP Queue

Querying the AMQP List

Querying an AMQP Queue

Generating an Access Credential

Parent topic: AMQP Data Forwarding