Checking Current Tenant's Development Mode

This API is used to check the development mode of the current tenant.

You can debug this API through automatic authentication in API Explorer or use the SDK sample code generated by API Explorer.

No identity policy-based permission required for calling this API.

GET https://{hostURL}/v4/tenant/develop-mode

**Table 1** Request header parameters
Parameter	Mandatory	Type	Description
X-Auth-Token	Yes	String	Definition User token. You can obtain the token by calling the IAM API used to obtain a user token. The value of X-Subject-Token in the response header is the user token. Constraints N/A Range A string that can contain 1 to 100,000 characters. Default Value N/A

Status code: 202

**Table 2** Response body parameters
Parameter	Type	Description
cr_enable	Boolean	Definition Whether to enable the change request mode.
repo_encryption_enabled	Boolean	Definition Whether to enable the encryption settings under the tenant.

Status code: 401

**Table 3** Response body parameters
Parameter	Type	Description
error_code	String	Definition Error code.
error_msg	String	Definition Error message.

Status code: 403

**Table 4** Response body parameters
Parameter	Type	Description
error_code	String	Definition Error code.
error_msg	String	Definition Error message.

GET https://{endpoint}/v4/tenant/develop-mode

Status code: 202

Check the development mode of the current tenant.

{
  "cr_enable" : true,
  "repo_encryption_enabled" : true
}

Status code: 401

Unauthorized

{
  "error_code" : "DEV.00000003",
  "error_msg" : "Authentication information expired."
}

Status code: 403

Bad Request

{
  "error_code" : "CH.004403",
  "error_msg" : "Insufficient permissions. Apply for the required permissions and try again."
}

Status Code	Description
202	Check the development mode of the current tenant.
401	Unauthorized
403	Bad Request

Parent topic: Tenant

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.

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