API Management FAQ

Q: What are the main functions provided by APIM?

A: APIM provides a complete API hosting service. Service users open capabilities, services, and data to partners and customers in the form of APIs.

  • Provide multiple methods such as attacks, request encryption, identity verification, and flow control to ensure API security and reduce API opening risks.
  • Provide full lifecycle management for the definition, release, debugging, and offlining of APIs, and generate API reference documents to improve API management and iteration efficiency.
  • Provide reporting, monitoring, and analysis functions to reduce API maintenance costs.

Q: What is the relationship between API, organization (OU), and EnOS application?

A: Organization users can create and mount APIs on APIM. The API belongs to the organization and can be called by the EnOS application to perform authentication with the application’s AccessKey and SecretKey.

Q: How do I call the API?

A: The EnOS API provides a series of developer tool kits to help developers efficiently complete device access, data collection, subscription to device data, and access to EnOS data and services without complex programming. For the detailed introduction, latest version, and download address of the EnOS SDK, visit EnOS Management Console > SDK Center. At the same time, all APIs can be called using token authentication. The AccessKey, SecretKey, and system timestamp are used to generate an Access Token by encryption, and the API is called using the Access Token.

Q: What are the dimensions of API monitoring?

A: Users can view the number of API requests, call delays, error analysis, and call success rates in the APIM Console.

Q: How can I ensure API security?


  • When creating an API, add OU authentication for API calls.
  • Set IP access control policies through whitelist / blacklist.
  • Set the flow control policy for the API, and set the QPS to the range that the backend service can support.

Q: Do I need to republish changes to the API?

A: After the API is published, if you edit the API parameters again, you need to republish to synchronize the modified information to the environment.