- Product Bulletin
- Service Overview
- Getting Started
-
User Guide
-
Working with FlexusRDS for MySQL
- Using IAM to Grant Access to FlexusRDS
- Buying a FlexusRDS for MySQL Instance
- Connecting to a FlexusRDS for MySQL Instance
- Suggestions on Using FlexusRDS for MySQL
- Data Migration
-
Instance Management
- Upgrading the Minor Version of a FlexusRDS for MySQL Instance
- Upgrading a FlexusRDS for MySQL Instance to an RDS DB Instance
- Changing the Name of a FlexusRDS for MySQL Instance
- Rebooting FlexusRDS for MySQL Instances
- Resetting the Administrator Password of a FlexusRDS for MySQL Instance
- Enabling Storage Autoscaling for a FlexusRDS for MySQL Instance
- Binding an EIP to a FlexusRDS for MySQL Instance or Unbinding an EIP from a FlexusRDS for MySQL Instance
- Changing the VPC and Subnet of a FlexusRDS for MySQL Instance
- Renewing FlexusRDS for MySQL Instances
- Unsubscribing from a FlexusRDS for MySQL Instance
- Backups and Restorations
- Parameters
- Monitoring
- Logs
- Interconnection with CTS
- FlexusRDS for MySQL Tags
- FlexusRDS for MySQL Quotas
-
Working with FlexusRDS for PostgreSQL
- Permissions Management
- Buying a FlexusRDS for PostgreSQL Instance
- Connecting to a FlexusRDS for PostgreSQL Instance
- Suggestions on Using FlexusRDS for PostgreSQL
- Data Migration
-
Instance Management
- Changing the Name of a FlexusRDS for PostgreSQL Instance
- Rebooting FlexusRDS for PostgreSQL Instances
- Resetting the Administrator Password of a FlexusRDS for PostgreSQL Instance
- Enabling Storage Autoscaling for a FlexusRDS for PostgreSQL Instance
- Binding an EIP to a FlexusRDS for PostgreSQL Instance or Unbinding an EIP from a FlexusRDS for PostgreSQL Instance
- Renewing FlexusRDS for PostgreSQL Instances
- Unsubscribing from a FlexusRDS for PostgreSQL Instance
-
Backups and Restorations
- Creating a Manual Backup for a FlexusRDS for PostgreSQL Instance
- Deleting a Manual Backup of a FlexusRDS for PostgreSQL Instance
- Downloading a Full Backup of a FlexusRDS for PostgreSQL Instance
- Checking and Exporting Backup Information of a FlexusRDS for PostgreSQL Instance
- Restoring a FlexusRDS for PostgreSQL Instance
- Parameters
- Monitoring Management
- Logs
- Interconnection with CTS
- FlexusRDS for PostgreSQL Tags
- FlexusRDS for PostgreSQL Quotas
-
Working with FlexusRDS for MySQL
- API Reference
-
FAQs
- What Is FlexusRDS?
- Can FlexusRDS for MySQL and RDS for MySQL Instances Access Each Other?
- Can I Change the Instance Class of My FlexusRDS Instance?
- Does FlexusRDS Support Cross-AZ HA?
- What Is the Backup Policy of FlexusRDS?
- How Are FlexusRDS Backups Billed?
- How Do I Download FlexusRDS Backups to Restore Data Locally?
- Why Does the Root User of My FlexusRDS for MySQL Instance Not Have Super Permissions?
- Which Storage Engine Does FlexusRDS for MySQL Provide?
- Why Does FlexusRDS for MySQL Not Support the MyISAM Storage Engine?
- Does FlexusRDS for MySQL Support Read Replicas?
- Why Can't I Ping the EIP After It Is Bound to My FlexusRDS for MySQL Instance?
- How Do I Create Accounts and Databases for My FlexusRDS Instance?
- What Major Versions and Minor Versions Does FlexusRDS for MySQL Support?
- Why Are Pay-per-Use Instances Not Provided by FlexusRDS?
- Can I Scale Up the Storage Space of My FlexusRDS for MySQL Instance?
- General Reference
Copied.
Response
Status Code
After sending a request, you will receive a response, including the status code, response header, and response body.
A status code is a group of digits ranging from 1xx to 5xx. It indicates the status of a response. For more information, see Status Codes.
For example, if status code 201 is returned for calling the API used to obtain a user token, the request is successful.
Response Header
Similar to a request, a response also has a header, for example, Content-Type.
Figure 1 shows the response header for the API used to obtain a user token. The x-subject-token header field is the desired user token. This token can then be used to authenticate the calling of other APIs.
(Optional) Response Body
This part is optional. The body of a response is often returned in structured format (for example, JSON or XML) as specified in the Content-Type header field. The response body transfers content except the response header.
{ "token": { "expires_at": "2019-02-13T06:52:13.855000Z", "methods": [ "password" ], "catalog": [ { "endpoints": [ { "region_id": "az-01", ......
{ "error_code": "AS.0001", "error_msg": "The format of message is error" }
In the response body, error_code is an error code, and error_msg provides information about the error.
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