Deletes a connection over an Express Connect circuit.

Limit

You can only delete a connection over an Express Connect circuit that is in the Rejected, Canceled, AllocationFailed, or Terminated state.

Debugging

OpenAPI Explorer automatically calculates the signature value. For your convenience, we recommend that you call this operation in OpenAPI Explorer. OpenAPI Explorer dynamically generates the sample code of the operation for different SDKs.

Request parameters

Parameter Type Required Example Description
Action String Yes DeletePhysicalConnection

The operation that you want to perform.

Set the value to DeletePhysicalConnection.

PhysicalConnectionId String Yes pc-119mfjzm7*********

The ID of the Express Connect circuit.

RegionId String Yes cn-shanghai

The region ID of the Express Connect circuit.

You can call the DescribeRegions operation to query the most recent region list.

ClientToken String No 02fb3da4-130e-11e9-8e44-0016e04115b

The client token that is used to ensure the idempotence of the request.

You can use the client to generate the value, but you must make sure that it is unique among different requests. The token can contain only ASCII characters and cannot exceed 64 characters in length.

Response parameters

Parameter Type Example Description
RequestId String 0ED8D006-F706-4D23-88ED-E11ED28DCAC0

The ID of the request

Examples

Sample requests

http(s)://[Endpoint]/?Action=DeletePhysicalConnection
&PhysicalConnectionId=pc-119mfjzm7*********
&RegionId=cn-shanghai
&<Common request parameters>

Sample success responses

XML format 

<DeletePhysicalConnectionResponse>
      <RequestId>0ED8D006-F706-4D23-88ED-E11ED28DCAC0</RequestId>
</DeletePhysicalConnectionResponse>

JSON format 

{
    "RequestId": "0ED8D006-F706-4D23-88ED-E11ED28DCAC0"
}

Error codes

HttpCode Error code Error message Description
404 InvalidPhysicalConnectionId.NotFound The PhysicalConnectionId provided does not exist in our records. The error message returned because the specified Express Connect circuit does not exist.
400 Forbidden.NotAllowedInState The request does not allow in this state. The error message returned because the connection is in an invalid state and the operation cannot be performed.
400 InvalidPhysicalConnectionId.NotMatched instance id not matched. The error message returned because the instance ID does not match.
400 Forbidden.VBRExists physical connection owner's vbr still exists. The error message returned because the virtual border router (VBR) of the Express Connect circuit still exists.
400 Forbidden.VBRExists vbr owner's vbr still exists. The error message returned because the VBR still exists.
400 Forbidden.AssociateToVBR The physical connection still associate to VBR. The error message returned because the Express Connect circuit is already associated with a VBR.

For a list of error codes, visit the API Error Center.