Why Did an Application Fail to Call an API?
- Check whether the network connection of the application is normal.
- Check whether the application access address and port number of the IoT platform in the request are correct.
- Run ping {application access address of the platform} to check whether the application can access the application access address of the platform.
- Run telnet {application access address of the platform } {port number} to check whether the application access port of the platform can be enabled.
- Check whether the application has been integrated with the platform certificate. The certificate can be downloaded from the Obtaining Resources page.
- Check whether the parameters are correctly set based on the API Reference.
- The validity period of accessToken returned by calling the Authentication API is one hour. After the validity period expires, other APIs cannot be called. In this case, call the Authentication API to obtain the new accessToken and then call other APIs again.
- If the previous steps do not resolve the issue, troubleshoot based on the error code returned when the API was called. For details about the error codes, see Error Codes. If an application has encapsulated error codes, you can use Postman to call the same API to obtain the original error code and description returned by the platform, and then rectify the fault based on the recommendations provided.
If the API for registering a device is called and a message is returned indicating that the device has been bound, check whether another device with the same verification code (IMEI or MAC address) exists under your account. If no device with the same verification code (IMEI or MAC address) is found under your account, contact the platform service provider to check whether the verification code (IMEI or MAC address) has been used on the platform.
Did this article solve your problem?
Thank you for your score!Your feedback would help us improve the website.