Moving APIs to Another Catalog

Function

This API is used to move APIs to another catalog.

Calling Method

For details, see Calling APIs.

URI

POST /v1/{project_id}/service/servicecatalogs/apis/batch-move

**Table 1** Path Parameters
Parameter	Mandatory	Type	Description
project_id	Yes	String	Project ID. For details about how to obtain the project ID, see Project ID and Account ID.

Request Parameters

**Table 2** Request header parameters
Parameter	Mandatory	Type	Description
X-Auth-Token	Yes	String	User token. This parameter is mandatory when token authentication is used. You can obtain it from the value of X-Subject-Token in the response message header returned by the "Obtaining a User Token" API of the IAM service.
workspace	Yes	String	Workspace ID. For details about how to obtain the workspace ID, see Instance ID and Workspace ID.
Dlm-Type	No	String	Specifies the version type of the data service. The value can be SHARED or EXCLUSIVE.
Content-Type	Yes	String	Type (format) of the message body. This parameter is mandatory if the message body exists. If the message body does not exist, leave this parameter blank. If the request body contains Chinese characters, use charset=utf8 to specify the Chinese character set, for example, application/json;charset=utf8.

**Table 3** Request body parameters
Parameter	Mandatory	Type	Description
target_pid	No	String	Parent catalog ID
apis	No	Array of strings	Directory to be moved.

Response Parameters

Status code: 400

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

Example Requests

Move APIs to another catalog.

/v1/0833a5737480d53b2f250010d01a7b88/service/servicecatalogs/apis/batch-move

{
  "target_pid" : "569e65bf4318b947ce5246e9d03c47e7",
  "apis" : [ "43ad1364493d7c04c8e09ae98d877527" ]
}