- Service Overview
- User Guide
-
API Reference
- Before You Start
- API Overview
- Calling APIs
- Application Examples
-
API v2 (Recommended)
- Agreement Management
- Attachment Management
- Service Ticket Management
- Service Ticket Permission Management
- Attachment Management
- Authorization Management
- Service Ticket Quota Management
-
Basic Ticket Configuration Query
- Querying Country/Region Code
- Querying Problem Type List
- Querying Additional Parameters
- Querying Problem Type Template
- Querying Service Ticket Category List
- Querying Product Type List
- Querying Region List
- Service Ticket Satisfaction Category List
- Querying Problem Severity List
- Querying Service Ticket Limits (Such As Limited CCs in an Email)
- Label Management
- Ticket Message Management
-
Ticket Query
- Querying Agency Information
- Querying Partner Service Ticket Permissions
- Statistics of Service Tickets in Various Statuses
- Querying Service Ticket Details
- Querying Service Ticket Operation Logs
- Querying Service Ticket CC
- Querying Service Ticket Status
- Querying Associated Partner Service Information
- Querying Service Ticket List Interface
- Querying Sub-User Information
- Management of Associated Tickets
- Verification Code Management
- Appendix
Show all
Basic Concepts
- Account
An account is created upon successful registration with the cloud platform. The account has full access permissions for all of its cloud services and resources. It can be used to reset user passwords and grant user permissions. The account is a payment entity and should not be used to perform routine management. For security purposes, create IAM users and grant them permissions for routine management.
- User
An IAM user is created using an account for cloud services. Each IAM user has its own identity credentials (password and access keys).
The domain name, username, and password will be required for API authentication.
- Region
Regions are geographic areas isolated from each other. Resources are region-specific and cannot be used across regions through internal network connections. For low network latency and quick resource access, select the nearest region.
- AZ
An availability zone (AZ) comprises of one or more physical data centers equipped with independent ventilation, fire, water, and electricity facilities. Computing, network, storage, and other resources in an AZ are logically divided into multiple clusters. AZs within a region are interconnected using high-speed optical fibers to support cross-AZ high-availability systems.
- Project
Projects group and isolate resources (including compute, storage, and network resources) across physical regions. A default project is provided for each region, and subprojects can be created under each default project. Users can be granted permissions to access all resources in a specific project. If you need more refined access control, you can create subprojects under a default project and purchase resources in subprojects. Then you can assign required permissions for users to access only resources in specific subprojects.
Figure 1 Project isolation model
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.