Creating the nacos Namespace

This API is used to create the nacos namespace.

POST /v1/{project_id}/nacos/v1/console/namespaces

**Table 1** Path Parameters
Parameter	Mandatory	Type	Description
project_id	Yes	String	Unique ID of a tenant's sub-project. The value contains 1 to 64 characters.

**Table 2** Query Parameters
Parameter	Mandatory	Type	Description
custom_namespace_id	Yes	String	Namespace ID. The value can contain a maximum of 128 characters, including uppercase letters, lowercase letters, digits, hyphens (-), and underscores (_).
namespace_name	Yes	String	Namespace name. The value can contain a maximum of 128 characters, excluding @, #, $, %, ^, &, and *.
namespace_desc	No	String	Namespace description. The value can contain a maximum of 256 characters.

**Table 3** Request header parameters
Parameter	Mandatory	Type	Description
X-Auth-Token	Yes	String	IAM-Token.
x-engine-id	Yes	String	Instance ID of an exclusive microservice engine.
X-Enterprise-Project-ID	Yes	String	Enterprise project ID.

Status code: 400

POST https://{endpoint}/v1/{project_id}/nacos/v1/console/namespaces

None

Status Code	Description
200	OK
400	Bad Request

Parent topic: Nacos API

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.