Creates an order for resource occupation of an Express Connect circuit.

Note You can call this operation only when the Express Connect circuit is in the (Complete) 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
RegionId String Yes cn-hangzhou

The ID of the region where the Express Connect circuit is deployed.

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

PhysicalConnectionId String Yes pc-bp1hp0wr072f6******

The ID of the Express Connect circuit.

Period Integer No 1

The subscription duration.

Note If InstanceChargeType is set to PrePaid, this parameter is required. You do not need to set this parameter when InstanceChargeType is set to PostPaid.
  • If PricingCycle is set to Month, set Period to a value from 1 to 9.
  • If PricingCycle is set to Year, set Period to a value from 1 to 5.
InstanceChargeType String No PrePaid

The billing method of the instance. Valid values:

PrePaid: subscription If you choose this billing method, make sure that your Alibaba Cloud account supports balance payments or credit payments.

AutoPay Boolean No false

Specifies whether to enable automatic payment.

  • true: enables automatic payment. Make sure that you have a sufficient balance in your account. Otherwise, your order becomes invalid and is automatically canceled.
  • false: disables automatic payment. This is the default value.
PricingCycle String No Month

The billing cycle of the subscription. Valid values:

  • Month: Bills are paid on a monthly basis. This is the default value.
  • Year: Bills are paid on an annual basis.
Action String Yes CreatePhysicalConnectionOccupancyOrder

The operation that you want to perform.

Set the value to CreatePhysicalConnectionOccupancyOrder.

ClientToken String No CBCE910E-D396-4944-8****

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 9B9300FE-11E2-4E3B-949C-BED3B44DD26D

The ID of the request.

Examples

Sample requests

http(s)://[Endpoint]/?Action=CreatePhysicalConnectionOccupancyOrder
&PhysicalConnectionId=pc-bp1hp0wr072f6******
&RegionId=cn-hangzhou
&Common request parameters

Sample success responses

XML format 

HTTP/1.1 200 OK
Content-Type:application/xml

<CreatePhysicalConnectionOccupancyOrderResponse>
    <RequestId>9B9300FE-11E2-4E3B-949C-BED3B44DD26D</RequestId>
</CreatePhysicalConnectionOccupancyOrderResponse>

JSON format 

HTTP/1.1 200 OK
Content-Type:application/json

{
  "RequestId" : "9B9300FE-11E2-4E3B-949C-BED3B44DD26D"
}

Error codes

HttpCode Error code Error message Description
400 Forbidden.NotAllowedInState The request does not allow in this state. The error message returned because the operation cannot be performed when the Express Connect circuit in the current state.
404 InvalidPhysicalConnectionId.NotFound The PhysicalConnectionId provided does not exist in our records. The error message returned because the Express Connect circuit does not exist.

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