Modifying the Current Edition

This API is used to obtain the current edition based on the project ID.

POST /v2/ss-service/{project_id}/editions

Table 1 describes the parameters.

**Table 1** Path parameters
Parameter	Mandatory	Type	Description
project_id	Yes	String	Tenant's project ID. See Obtaining a Project ID.

**Table 2** Request header parameters
Parameter	Mandatory	Type	Description
Content-Type	Yes	String	Message body type (format). Default value: application/json;charset=utf8.
X-Auth-Token	Yes	String	API calling can be authenticated using a token or AK/SK. If you use a token, this parameter is mandatory and must be set to the token. For details about how to obtain a token, see Obtaining a User Token.

**Table 3** Request body parameters
Parameter	Mandatory	Type	Description
projectId	Yes	String	Tenant's project ID. See Obtaining a Project ID.
resourceSpecCode	No	String	Edition type. Value: servicestage.professional or servicestage.basic.

None

None

{
 "project_id": "xxx",
 "resourceSpecCode": "servicestage.professional",
 "applications": 1
}

Status Code	Description
200	OK
400	Bad Request

The error code format is SVCSTG.BILLING.[Error_ID], for example, SVCSTG.BILLING.5004401. For details, see ServiceStage Error Codes.

Parent topic: Service Transparent Transmission

Thank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.

The system is busy. Please try again later.

Which of the following issues have you encountered?

Content is inconsistent with the product UI

Unclear descriptions

Lack of examples or code

Incorrect steps

Can't find what I need

Lack of best practices

Feedback (optional)

0/500

Select at least one type of issue, and enter your comments or suggestions.

Enter a maximum of 500 characters.

Submit Cancel

For any further questions, feel free to contact us through the chatbot.