Creates an order for resource occupation of one or more physical connections.

Note You can call this operation for only a physical connection that 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
Action String Yes CreatePhysicalConnectionOccupancyOrder

The operation that you want to perform.

Set the value to CreatePhysicalConnectionOccupancyOrder.

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

The ID of the physical connection.
RegionId String Yes cn-hangzhou

The ID of the region where the physical connection is deployed.
Period Integer No 1

The subscription duration.

  • If PricingCycle is set to Month, Period can be set from 1 to 9.
  • If PricingCycle is set to Year, Period can be set from 1 to 5.

This parameter is required when InstanceChargeType is set to PrePaid. Ignore this parameter when InstanceChargeType is set to PostPaid.

InstanceChargeType String No PostPaid

The billing method of the physical connection. Valid values:

  • PrePaid: subscription. If you choose this billing method, make sure that you Alibaba Cloud account supports balance payments or credit payments.
  • PostPaid: pay-as-you-go. This is the default value.
AutoPay Boolean No true

Specifies whether to enable automatic payments. Valid values:

  • true: enables automatic payments. This is the default value. Make sure that your Alibaba Cloud account has sufficient balance. Otherwise, your orders become invalid and must be canceled.
  • false: An order is generated but no payment is made.
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.
ClientToken String No CBCE910E-D396-4944-8****

The client token that is used to ensure the idempotence of the request. You must ensure that Client Token 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 

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

JSON format 

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

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 physical connection does not exist.
400 Forbidden.NotAllowedInState The request does not allow in this state. The error message returned because the state does not support this operation.

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