Help Center/
Customer Engagement Center/
API Reference/
Monitoring Interface Reference/
Interface Description
Updated on 2025-11-13 GMT+08:00
Interface Description
- In AICC 8.13.0 and later versions, the following structures returned by all third-party interfaces are not recommended. The following structures are used to be compatible with versions earlier than 8.13.0. In 8.13.0 and later versions, resultCode instead of result is used as the result code, and resultDesc instead of resultDatas is used as the data returned by the interface.
Parameter
Type
Description
result
String
Query result. The options are as follows:
- 0: success
- Other values: failure
resultDatas
List <JSONObject>
Object array in the returned result after a successful query.
- The NSLB server IP address and port number involved in the request URLs of all interfaces in the following sections vary according to the deployment mode.
- SaaS public cloud scenario: The NSLB server IP address is the IP address of the outer NSLB server (providing external access to virtualized services), and the port number is the port number provided for external services (corresponding to aicc-webproxy in NSLB routing rules). The default port number is 28050.
- OP integrated deployment and OP independent deployment scenarios: The NSLB server IP address is the IP address of the NSLB server corresponding to the CC-CMS, and the port number is the port number provided for external services (corresponding to aicc-openproxy in NSLB routing rules). The default port number is 28080.
- Real-Time Data Query
- Historical Data Query
- Configuration Data Query
- Inspection Relationship Maintenance Interfaces
- Querying Outbound Call Task Lists
- Interfaces for Querying System Indicators
- Checking Cluster Health Status
- Interface for Uploading Logs
- Downloading Inspection Recording Files
Parent topic: Monitoring Interface Reference
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.
The system is busy. Please try again later.
For any further questions, feel free to contact us through the chatbot.
Chatbot