All Products
Search
Document Center

Lindorm:ModifyInstancePayType

Last Updated:Oct 27, 2025

Changes the billing method of a Lindorm instance.

Operation description

You can call this operation to switch the billing method of an instance between subscription and pay-as-you-go.

Before you call this operation, make sure that you understand the billing methods and pricing of Lindorm.

Try it now

Try this API in OpenAPI Explorer, no manual signing needed. Successful calls auto-generate SDK code matching your parameters. Download it with built-in credential security for local usage.

Test

RAM authorization

No authorization for this operation. If you encounter issues with this operation, contact technical support.

Request parameters

Parameter

Type

Required

Description

Example

InstanceId

string

Yes

The ID of the instance.

ld-bp1z3506imz2f****

Duration

integer

Yes

The subscription duration. This parameter is required when you change the billing method to subscription.

  • If `PricingCycle` is `Month`, the valid values are 1 to 9.

  • If `PricingCycle` is `Year`, the valid values are 1 to 3.

1

PricingCycle

string

No

The unit of the subscription duration. This parameter is required when you change the billing method to subscription.

  • Month: The unit is month.

  • Year: The unit is year.

Month

PayType

string

Yes

The billing method of the instance. Valid values:

  • PREPAY: subscription.

  • POSTPAY: pay-as-you-go.

POSTPAY

Response elements

Element

Type

Description

Example

object

The response.

RequestId

string

The request ID.

587BCA54-50DA-4885-ADE9-80A848339151

OrderId

integer

The order ID.

211662251220224

InstanceId

string

The instance ID.

ld-bp1z3506imz2f****

AccessDeniedDetail

string

The detailed reason why the access is denied.

{"AuthAction":"xxx","AuthPrincipalDisplayName":"222","AuthPrincipalOwnerId":"111","AuthPrincipalType":"SubUser",,"NoPermissionType":"ImplicitDeny","PolicyType":"AccountLevelIdentityBasedPolicy","EncodedDiagnosticMessage":"xxxxxx"}

Examples

Success response

JSON format

{
  "RequestId": "587BCA54-50DA-4885-ADE9-80A848339151",
  "OrderId": 211662251220224,
  "InstanceId": "ld-bp1z3506imz2f****",
  "AccessDeniedDetail": "{\"AuthAction\":\"xxx\",\"AuthPrincipalDisplayName\":\"222\",\"AuthPrincipalOwnerId\":\"111\",\"AuthPrincipalType\":\"SubUser\",,\"NoPermissionType\":\"ImplicitDeny\",\"PolicyType\":\"AccountLevelIdentityBasedPolicy\",\"EncodedDiagnosticMessage\":\"xxxxxx\"}"
}

Error codes

HTTP status code

Error code

Error message

Description

400 Instance.IsDeleted The instance is deleted. The specified instance is already deleted.
400 Instance.IsNotAvailable The instance is unavailable. The specified instance is unavailable.
403 API.Forbidden The API operation is forbidden in this environment. This operation is not supported in the current environment.
403 Lindorm.Errorcode.OperationDenied You are not authorized to operate on the specified resource. You are not authorized to manage the specified resource.
403 Lindorm.Errorcode.ServiceLinkedRoleNoPermission No permission to create service linked role. You are not authorized to create the service-linked role.
404 Lindorm.Errorcode.InstanceNotFound The instance is not found. The specified instance does not exist.

See Error Codes for a complete list.

Release notes

See Release Notes for a complete list.