CreatePostPayOrder - ApsaraMQ for Kafka - Alibaba Cloud Documentation Center

Creates a pay-as-you-go ApsaraMQ for Kafka instance. Pay-as-you-go instances allow you to pay after you use the resources. You are charged for pay-as-you-go instances based on the actual resource usage. You can use pay-as-you-go instances in test scenarios or scenarios in which the peak traffic is uncertain.

Operation description

Before you call this operation, make sure that you understand the billing method and pricing of pay-as-you-go Message Queue for Apache Kafka instances. For more information, see Billing .

Debugging

OpenAPI Explorer automatically calculates the signature value. For your convenience, we recommend that you call this operation in OpenAPI Explorer.

Debug

Authorization information

The following table shows the authorization information corresponding to the API. The authorization information can be used in the Action policy element to grant a RAM user or RAM role the permissions to call this API operation. Description:

Operation: the value that you can use in the Action element to specify the operation on a resource.
Access level: the access level of each operation. The levels are read, write, and list.
Resource type: the type of the resource on which you can authorize the RAM user or the RAM role to perform the operation. Take note of the following items:
- The required resource types are displayed in bold characters.
- If the permissions cannot be granted at the resource level, All Resources is used in the Resource type column of the operation.
Condition Key: the condition key that is defined by the cloud service.
Associated operation: other operations that the RAM user or the RAM role must have permissions to perform to complete the operation. To complete the operation, the RAM user or the RAM role must have the permissions to perform the associated operations.

Operation	Access level	Resource type	Condition key	Associated operation
alikafka:CreatePostPayOrder	Write	All Resources *	alikafka:DeployModule alikafka:SpecType	none

Request parameters

Parameter	Type	Required	Description	Example
RegionId	string	Yes	The region ID of the instance.	cn-hangzhou
DiskType	string	Yes	The disk type. Valid values: 0: ultra disk 1: standard SSD	0
DiskSize	integer	Yes	The disk size. For more information about the valid values, see Billing .	500
DeployType	integer	Yes	The deployment mode of the instance. Valid values: 4: deploys the instance that allows access from the Internet and a VPC. 5: deploys the instance that allows access only from a VPC.	5
EipMax	integer	No	The Internet traffic for the instance. This parameter is required if the DeployType parameter is set to 4. For more information about the valid values, see Billing .	0
IoMax	integer	No	The maximum traffic for the instance. We recommend that you do not configure this parameter. You must specify at least one of the IoMax and IoMaxSpec parameters. If you configure both parameters, the value of the IoMaxSpec parameter takes effect. We recommend that you specify only the IoMaxSpec parameter. For more information about the valid values, see Billing .	20
PartitionNum	integer	No	The number of partitions. We recommend that you configure this parameter. You must specify at least one of the PartitionNum and TopicQuota parameters. We recommend that you configure only the PartitionNum parameter. If you specify both parameters, the topic-based sales model is used to check whether the PartitionNum value and the TopicQuota value are the same. If they are not the same, a failure response is returned. If they are the same, the order is placed based on the PartitionNum value. For more information about the valid values, see Billing .	50
TopicQuota	integer	No	The number of topics. We recommend that you do not configure this parameter. You must specify at least one of the PartitionNum and TopicQuota parameters. We recommend that you configure only the PartitionNum parameter. If you specify both parameters, the topic-based sales model is used to check whether the PartitionNum value and the TopicQuota value are the same. If they are not the same, a failure response is returned. If they are the same, the order is placed based on the PartitionNum value. The default value of the TopicQuota parameter varies based on the value of the IoMaxSpec parameter. If the number of topics that you consume exceeds the default value, you are charged additional fees. For more information about the valid values, see Billing .	50
SpecType	string	No	The edition of the instance. Valid values: normal: Standard Edition (High Write) professional: Professional Edition (High Write) professionalForHighRead: Professional Edition (High Read) For more information about these instance editions, see Billing .	normal
IoMaxSpec	string	No	The traffic specification of the instance. We recommend that you configure this parameter. You must specify at least one of the IoMax and IoMaxSpec parameters. If you configure both parameters, the value of the IoMaxSpec parameter takes effect. We recommend that you specify only the IoMaxSpec parameter. For more information about the valid values, see Billing .	alikafka.hw.2xlarge
ResourceGroupId	string	No	The ID of the resource group. If this parameter is left empty, the default resource group is used. You can view the resource group ID on the Resource Group page in the Resource Management console.	rg-ac***********7q
Tag	object []	No	The tags.
Key	string	Yes	The key of tag N. Valid values of N: 1 to 20. If this parameter is left empty, the keys of all tags are matched. The tag key must be up to 128 characters in length. It cannot start with acs: or aliyun or contain http:// or https://.	FinanceDept
Value	string	No	The value of tag N. Valid values of N: 1 to 20. If you do not specify a tag key, you cannot specify a tag value. If this parameter is not configured, all tag values are matched. The tag value must be 1 to 128 characters in length. It cannot start with acs: or aliyun or contain http:// or https://.	FinanceJoshua

Response parameters

Parameter	Type	Description	Example
	object
Code	integer	The HTTP status code returned. The HTTP status code 200 indicates that the request is successful.	200
Message	string	The message returned.	operation success.
RequestId	string	The ID of the request.	06084011-E093-46F3-A51F-4B19A8AD****
Success	boolean	Indicates whether the request is successful.	true
OrderId	string	The ID of the order.	20497346575****

Examples

Sample success responses

JSONformat

{
  "Code": 200,
  "Message": "operation success.",
  "RequestId": "06084011-E093-46F3-A51F-4B19A8AD****",
  "Success": true,
  "OrderId": "20497346575****"
}

Error codes

HTTP status code	Error code	Error message
400	Invalid.%s	Invalid.%s
400	BIZ.LIMIT.QUOTA.DOWN	Invalid.%s
400	BIZ.LIMIT.QUOTA.DOWN.1	Invalid.%s
400	BIZ.LIMIT.QUOTA.DOWN.2	Invalid.%s
400	Invalid.Partition.%s	Invalid.%s
400	BIZ_FIELD_CHECK_INVALID	%s. Please check and try again later.

For a list of error codes, visit the Service error codes.

Change history

Change time

Summary of changes

Operation

2022-10-28

The Error code has changed. The request parameters of the API has changed

see changesets

Change item	Change content
Error Codes	The Error code has changed.
	delete Error Codes: 400
Input Parameters	The request parameters of the API has changed.
	Added Input Parameters: Tag

2022-08-31

The Error code has changed

see changesets

Change item	Change content
Error Codes	The Error code has changed.
	delete Error Codes: 400