Help Center/ GeminiDB/ API Reference/ APIs v3 (Recommended)/ Instances/ Deleting a Memory Mapping
Updated on 2025-11-17 GMT+08:00
View PDF
Share

Deleting a Memory Mapping

Function

This API is used to delete a memory mapping.

Constraints

This API can be used only on primary/standby GeminiDB Redis instances.

Authorization

Each account is authorized to call all APIs, but its IAM users must be granted necessary permissions. For details, see Permission Policies and Supported Actions.

URI

DELETE /v3/{project_id}/dbcache/mapping

Table 1 URI parameters

Parameter

Mandatory

Type

Description

project_id

Yes

String

Explanation:

Project ID of a tenant in a region. To obtain this value, see Obtaining a Project ID.

Constraints:

N/A

Values:

N/A

Default value:

N/A

Request Parameters

Table 2 Request header parameters

Parameter

Mandatory

Type

Description

X-Auth-Token

Yes

String

Explanation:

User token

You can obtain the token by calling the IAM API by following Obtaining a User Token Through Password Authentication.

Constraints:

N/A

Values:

N/A

Default value:

N/A
Table 3 Request body parameters

Parameter

Mandatory

Type

Description

id

Yes

String

Explanation:

Memory acceleration mapping ID

Constraints:

N/A

Values:

N/A

Default value:

N/A

Response Parameters

Status code: 202

Table 4 Response body parameters

Parameter

Type

Description

job_id

String

Explanation:

Task ID

Constraints:

N/A

Values:

N/A

Default value:

N/A

Example Request

DELETE https://{endpoint}/v3/054e292c9880d4992f02c0196d3ea468/dbcache/mapping 
 
{ 
  "id":     "1094e5d3-c140-4095-9b13-242de267c175" 
}

Example Response

Status code: 202

Accepted.

{ 
  "job_id" : "04efe8e2-9255-44ae-a98b-d87cae411890" 
}

Status Codes

For details, see Status Codes.

Error Codes

For details, see Error Codes.

Parent topic: Instances