El contenido no se encuentra disponible en el idioma seleccionado. Estamos trabajando continuamente para agregar más idiomas. Gracias por su apoyo.
- What's New
- Product Bulletin
- Service Overview
- Billing
-
Getting Started
-
Quick Device Access - Property Reporting and Command Receiving
- Subscribing to IoTDA
- Connecting a Smart Smoke Detector to the Platform (Quick Usage)
- Registering a Simulated Smart Street Light Device
- Using MQTT.fx to Simulate Communication Between the Smart Street Light and the Platform
- Using a Virtual Smart Street Light to Communicate with the Platform (Java SDK)
- Using a Virtual Smart Street Light to Communicate with the Platform (C SDK)
- Quick Device Access - Message Sending and Receiving
- Quick Application Access
-
Quick Device Access - Property Reporting and Command Receiving
-
User Guide
- Overview
- IoTDA Instances
- Resource Spaces
- Device Access
- Message Communications
- Device Management
-
Rules
- Overview
- Data Forwarding Process
- SQL Statements
- Connectivity Tests
- Data Forwarding to Huawei Cloud Services
- Data Forwarding to Third-Party Applications
- Data Forwarding Channel Details
- Data Forwarding Stack Policies
- Data Forwarding Flow Control Policies
- Abnormal Data Target
- Device Linkage
- Monitoring and O&M
- Granting Permissions Using IAM
-
Best Practices
- Introduction
-
Device Access
- Developing an MQTT-based Simulated Smart Street Light Online
- Developing a Smart Street Light Using NB-IoT BearPi
- Developing a Smart Smoke Detector Using NB-IoT BearPi
- Connecting and Debugging an NB-IoT Smart Street Light Using a Simulator
- Developing a Protocol Conversion Gateway for Access of Generic-Protocol Devices
- Connecting a Device That Uses the X.509 Certificate Based on MQTT.fx
- Connecting to IoTDA Based on the BearPi-HM_Nano Development Board and OpenHarmony 3.0
- Testing MQTT Performance Using JMeter
- Device Management
- Data Forwarding
- Device Linkage
-
Developer Guide
- Before You Start
- Obtaining Resources
- Product Development
- Development on the Device Side
- Development on the Application Side
-
API Reference
-
API Reference on the Application Side
- Before You Start
- Calling APIs
- API Overview
-
API
- Product Management
- Device Management
- Device Message
- Device Command APIs
- Device Property
- AMQP Queue Management
- Access Credential Management
- Data Forwarding Rule Management
-
Transition Data
- Push a Device Status Change Notification
- Push a Device Property Reporting Notification
- Push a Device Message Status Change Notification
- Push a Batch Task Status Change Notification
- Push a Device Message Reporting Notification
- Push a Device Addition Notification
- Push a Device Update Notification
- Push a Device Deletion Notification
- Push a Product Addition Notification
- Push a Product Update Notification
- Push a Product Deletion Notification
- Push an Asynchronous Device Command Status Change Notification
- Rule Management
- Device Shadow
- Group Management
- Tag Management
- Instance Management
- Resource Space Management
- Batch Task
- Device CA Certificate Management
- OTA Upgrade Package Management
- Message Broadcasting
- Device Tunnel Management
- Stack policy management
- Flow control policy management
- Device Proxy
- Device Policy Management
- Bridge Management
- Pre-provisioning Template Management
- Custom Authentication
- Codec Function Management
- Permissions and Supported Actions
- Examples
- Appendix
-
MQTT or MQTTS API Reference on the Device Side
- Before You Start
- Communication Modes
- Topics
- Device Connection Authentication
- Device Commands
- Device Messages
- Device Properties
-
Gateway and Child Device Management
- Platform Notifying a Gateway of New Child Device Connection
- Platform Notifying a Gateway of Child Device Deletion
- Gateway Synchronizing Child Device Information
- Gateway Updating Child Device Status
- Responding to a Request for Updating Child Device Statuses
- Gateway Requesting for Adding Child Devices
- Platform Responding to a Request for Adding Child Devices
- Gateway Requesting for Deleting Child Devices
- Platform Responding to a Request for Deleting Child Devices
- Software and Firmware Upgrade
- File Upload and Download
- Device Time Synchronization
- Device Reporting Information
- Device Log Collection
- Remote Configuration
- Device Tunnel Management
- HTTPS API Reference on the Device Side
- LwM2M API Reference on the Device Side
- Security Tunnel WebSocket API Reference
- Module AT Command Reference
- Change History
-
API Reference on the Application Side
- SDK Reference
-
FAQs
- Top FAQs
-
Solution Consulting
- In What Scenarios Can the IoT Platform Be Applied?
- What Are the Changes Brought by the Integration of IoT Device Management and IoTDA?
- Can I Enable IoTDA for IAM Users or Sub-Projects?
- Which Regions of Huawei Cloud Are Supported by the IoT Platform?
- Does Huawei Provide Modules, Hardware Devices, and Application Software?
- What Should I Do If I Want to Call an API But Have No Permissions to Do So as an IAM User? (Is It Edition-specific?)
- Why Was I Prompted to Grant Security Administrator Permissions When I Create a Rule or Set Resource File Storage?
- Which Resource Space Will Be Set As Default on the IoT Platform?
- How Does IoTDA Obtain Device Data?
- Is There Any Limitation on the Number of Resource Spaces and Devices I Can Add on the IoT Platform?
- Does the IoTDA Support Device Registration in Batches?
- Are There Any Limitations on the Use of the IoT Platform?
- What DTLS Encryption Algorithms Are Supported by the IoT Platform?
- Does the IoT Platform Support Conversion Between Big-Endian and Little-Endian for Binary Data?
- What Is NB-IoT?
- What Are the Components of the IoT Platform and What Hardware Architectures Does It Support?
- How Do I Obtain the Platform Access Address?
- Device Integration
- IoT Device SDKs
- LwM2M/CoAP Device Access
- MQTT-based Device Access
- Products Models
- Message Communications
- Subscription and Push
- Codecs
- OTA Upgrades
- Application Integration
- General Reference
Show all
Copied.
Status Code
Table 1 describes status codes.
Status Code |
Code |
Error Code Description |
---|---|---|
100 |
Continue |
The client should continue sending the request. This interim response is used to inform the client that the initial part of the requests has been received and not rejected by the server. |
101 |
Switching Protocols |
The requester has asked the server to switch protocols and the server has agreed to do so. The protocol should be switched only when it is advantageous to do so. For example, the protocol in use is switched to a later version of HTTP. |
201 |
Created |
The request has been fulfilled, resulting in the creation of a new resource. |
202 |
Accepted |
The request has been accepted, but the processing has not been completed. |
203 |
Non-Authoritative Information |
The request has been fulfilled. |
204 |
NoContent |
The server has successfully processed the request, but does not return any response. The status code is returned in response to an HTTP OPTIONS request. |
205 |
Reset Content |
The server successfully processed the request, but is not returning any content. |
206 |
Partial Content |
The server has fulfilled the partial GET request for the resource. |
300 |
Multiple Choices |
There are multiple options for the resource from which the client may choose. For example, this code could be used to present a list of resource characteristics and addresses from which the client, such as a browser, may choose. |
301 |
Moved Permanently |
This and all future requests should be permanently directed to the given URI indicated in this response. |
302 |
Found |
The requested resource was temporarily moved. |
303 |
See Other |
The response to the request can be found under another URI using a GET or POST method. |
304 |
Not Modified |
The requested resource has not been modified. In such case, there is no need to retransmit the resource since the client still has a previously downloaded copy. |
305 |
Use Proxy |
The requested resource must be accessed through a proxy. |
306 |
Unused |
This HTTP status code is no longer used. |
400 |
BadRequest |
The request could not be understood by the server due to malformed syntax. The client should not repeat the request without modifications. |
401 |
Unauthorized |
The authorization information provided by the client is incorrect or invalid. |
402 |
Payment Required |
Reserved for future use. |
403 |
Forbidden |
The request is rejected. The client should not repeat the request without modifications. |
404 |
NotFound |
The requested resource cannot be found. The client should not repeat the request without modifications. |
405 |
MethodNotAllowed |
A request method is not supported for the requested resource. The client should not repeat the request without modifications. |
406 |
Not Acceptable |
The server cannot fulfill the request based on the content characteristics of the request. |
407 |
Proxy Authentication Required |
This code is similar to 401, but indicates that the client must first authenticate itself with the proxy. |
408 |
Request Time-out |
The client does not produce a request within the time that the server was prepared to wait. The client may re-initiate the request without any modification at any time. |
409 |
Conflict |
The request could not be completed due to a conflict with the current state of the resource. The resource that the client attempts to create already exists, or the request fails to be processed because of the update of the conflict request. |
410 |
Gone |
The requested resource is no longer available. The requested resource has been deleted permanently. |
411 |
Length Required |
The server refused to process the request because the request does not specify the length of its content. |
412 |
Precondition Failed |
The server does not meet one of the preconditions that the requester puts on the request. |
413 |
Request Entity Too Large |
The server is refusing to process a request because the request entity is larger than the server is willing or able to process. The server may close the connection to prevent the client from continuing the request. If the server temporarily cannot process the request, the response will contain a Retry-After header field. |
414 |
Request-URI Too Large |
The server is refusing to service the request because the request URI is longer than the server is willing to interpret. |
415 |
Unsupported Media Type |
The server is refusing to service the request because the entity of the request is in a format not supported by the requested resource for the requested method. |
416 |
Requested range not satisfiable |
The requested range is invalid. |
417 |
Expectation Failed |
The server fails to meet the requirements of the Expect request-header field. |
422 |
UnprocessableEntity |
The request was well-formed but was unable to be followed due to semantic errors. |
429 |
TooManyRequests |
The client sends excessive requests to the server within a given time (exceeding the limit on the access frequency of the client), or the server receives excessive requests within a given time (beyond its processing capability). In this case, the client should repeat requests after the time specified in the Retry-After header of the response expires. |
500 |
InternalServerError |
The server encountered an unexpected condition which prevented it from fulfilling the request. |
501 |
Not Implemented |
The server does not support the functionality required to fulfill the request. |
502 |
Bad Gateway |
The server acting as a gateway or proxy receives an invalid response from a remote server. |
503 |
ServiceUnavailable |
The requested service is unavailable. The client should not repeat the request without modifications. |
504 |
ServerTimeout |
The request cannot be fulfilled within a given amount of time. This status code is returned to the client only when the timeout parameter is specified in the request. |
505 |
HTTP Version not supported |
The server does not support the HTTP protocol version used in the request. |
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot