Adding a Backup (1.0.0)

Add a backup. If data in the current graph is incorrect or faulty, you can start the backup graph to restore the data.

POST /v2/{project_id}/graphs/{graph_id}/backups

**Table 1** URI parameters
Parameter	Mandatory	Type	Description
project_id	Yes	String	Project ID. For details about how to obtain the project ID, see Obtaining a Project ID.
graph_id	Yes	String	Graph ID

**Table 2** Request header parameter
Parameter	Mandatory	Type	Description
X-Auth-Token	Yes	String	User token. It is used to obtain the permission to call APIs. For details about how to obtain the token, see Authentication. The value of X-Subject-Token in the response header is the token.

Status code: 200

**Table 3** Response body parameters
Parameter	Type	Description
job_id	String	ID of the graph backup job. NOTE: You can view the job execution status and obtain the return result by querying the job ID. For details, see Task Center APIs.

Status code: 400

**Table 4** Response body parameters
Parameter	Type	Description
error_code	String	System prompt code. If execution succeeds, this parameter may be left blank. If execution fails, this parameter is used to display the error code.
error_msg	String	System prompt code. If execution succeeds, this parameter may be left blank. If execution fails, this parameter is used to display the error message.

Add a graph backup.

POST https://Endpoint/v2/{project_id}/graphs/{graph_id}/backups

{ }

Status code: 200

Example response for a successful request

{
  "job_id" : "ff8080815f9a3c84015f9a438ff70001"
}

Status code: 400

Example response for a failed request

{
  "error_code" : "GES.7000",
  "error_msg" : "The graph does not exist or has been deleted."
}