Querying VPC Channels
Function
This API is used to query the VPC channels under a gateway.
Debugging
You can use API Explorer to debug this API.
URI
GET /v2/{project_id}/apigw/instances/{instance_id}/vpc-channels
|
Parameter |
Mandatory |
Type |
Description |
|---|---|---|---|
|
project_id |
Yes |
String |
Project ID. For details about how to obtain a project ID, see "Appendix" > "Obtaining a Project ID" in this document. |
|
instance_id |
Yes |
String |
Gateway ID. |
|
Parameter |
Mandatory |
Type |
Description |
|---|---|---|---|
|
offset |
No |
Long |
Offset from which the query starts. If the value is less than 0, it is automatically converted to 0. Default: 0 |
|
limit |
No |
Integer |
Number of records displayed on each page. Minimum: 1 Maximum: 500 Default: 20 |
|
id |
No |
String |
VPC channel ID. |
|
name |
No |
String |
VPC channel name. |
|
precise_search |
No |
String |
Parameter name (name) for exact matching. |
Request Parameters
|
Parameter |
Mandatory |
Type |
Description |
|---|---|---|---|
|
X-Auth-Token |
Yes |
String |
User token, which can be obtained by calling the IAM API used to obtain a user token. The value of X-Subject-Token in the response header is the user token. |
Response Parameters
Status code: 200
|
Parameter |
Type |
Description |
|---|---|---|
|
size |
Integer |
Length of the returned resource list. |
|
total |
Long |
Number of resources that match the query conditions. |
|
vpc_channels |
Array of VpcChannelInfo objects |
VPC channel list. |
|
Parameter |
Type |
Description |
|---|---|---|
|
name |
String |
VPC channel name. A VPC channel name can contain 3 to 64 characters, starting with a letter. Only letters, digits, hyphens (-), and underscores (_) are allowed. Chinese characters must be in UTF-8 or Unicode format. |
|
port |
Integer |
Host port of the VPC channel. This parameter is valid only when the VPC channel type is set to 2. The value range is 1–65535. This parameter is required if the VPC channel type is set to 2. |
|
balance_strategy |
Integer |
Distribution algorithm.
This parameter is mandatory if the VPC channel type is set to 2. Default: 1 Enumeration values:
|
|
member_type |
String |
Member type of the VPC channel.
This parameter is required if the VPC channel type is set to 2. Default: ecs Enumeration values:
|
|
create_time |
String |
Time when the VPC channel is created. |
|
id |
String |
VPC channel ID. |
|
status |
Integer |
VPC channel status.
Enumeration values:
|
|
member_groups |
Array of MemberGroupInfo objects |
Backend cloud server groups. Currently, this parameter is not supported. |
|
Parameter |
Type |
Description |
|---|---|---|
|
member_group_name |
String |
Name of the backend server group of the VPC channel. |
|
member_group_remark |
String |
Description of the backend server group. |
|
member_group_weight |
Integer |
Weight of the backend server group. If the server group contains servers and a weight has been set for it, the weight is automatically used to assign weights to servers in this group. Minimum: 0 Maximum: 100 |
|
dict_code |
String |
Dictionary code of the backend server group. The value can contain letters, digits, hyphens (-), underscores (_), and periods (.). Currently, this parameter is not supported. Minimum: 3 Maximum: 64 |
|
member_group_id |
String |
ID of the backend server group of the VPC channel. |
|
create_time |
String |
Time when the backend server group is created. |
|
update_time |
String |
Time when the backend server group is updated. |
Status code: 400
|
Parameter |
Type |
Description |
|---|---|---|
|
error_code |
String |
Error code. |
|
error_msg |
String |
Error message. |
Status code: 401
|
Parameter |
Type |
Description |
|---|---|---|
|
error_code |
String |
Error code. |
|
error_msg |
String |
Error message. |
Status code: 403
|
Parameter |
Type |
Description |
|---|---|---|
|
error_code |
String |
Error code. |
|
error_msg |
String |
Error message. |
Status code: 404
|
Parameter |
Type |
Description |
|---|---|---|
|
error_code |
String |
Error code. |
|
error_msg |
String |
Error message. |
Status code: 500
|
Parameter |
Type |
Description |
|---|---|---|
|
error_code |
String |
Error code. |
|
error_msg |
String |
Error message. |
Example Requests
None
Example Responses
Status code: 200
OK
{
"total" : 2,
"size" : 2,
"vpc_channels" : [ {
"member_type" : "instance",
"balance_strategy" : 1,
"create_time" : "2020-07-23T07:24:33Z",
"port" : 8080,
"name" : "VPC_Channel_1",
"id" : "105c6902457144a4820dff8b1ad63331",
"type" : 1,
"status" : 1
}, {
"member_type" : "ip",
"balance_strategy" : 2,
"create_time" : "2020-07-23T07:11:57Z",
"port" : 8088,
"name" : "VPC_Channel_2",
"id" : "56a7d7358e1b42459c9d730d65b14e59",
"type" : 2,
"status" : 1
} ]
}
Status code: 400
Bad Request
{
"error_code" : "APIG.2011",
"error_msg" : "The request parameters must be specified,parameterName:name. Please refer to the support documentation"
}
Status code: 401
Unauthorized
{
"error_code" : "APIG.1002",
"error_msg" : "Incorrect token or token resolution failed"
}
Status code: 403
Forbidden
{
"error_code" : "APIG.1005",
"error_msg" : "No permissions to request this method"
}
Status code: 404
Not Found
{
"error_code" : "APIG.3030",
"error_msg" : "The instance does not exist;id:eddc4d25480b4cd6b512f270a1b8b341"
}
Status code: 500
Internal Server Error
{
"error_code" : "APIG.9999",
"error_msg" : "System error"
}
Status Codes
|
Status Code |
Description |
|---|---|
|
200 |
OK |
|
400 |
Bad Request |
|
401 |
Unauthorized |
|
403 |
Forbidden |
|
404 |
Not Found |
|
500 |
Internal Server Error |
Error Codes
See Error Codes.
Last Article: Querying Details of a VPC Channel
Next Article: Adding Backend Servers
Did this article solve your problem?
Thank you for your score!Your feedback would help us improve the website.