--- title: "Re-encrypt" slug: "security-kms-reencrypt" tags: ["Key Management Service", "KMS"] updated: 2026-09-17T10:25:45Z published: 2026-09-17T10:25:45Z canonical: "api.ncloud-docs.com/security-kms-reencrypt" --- > ## Documentation Index > Fetch the complete documentation index at: https://api.ncloud-docs.com/llms.txt > Use this file to discover all available pages before exploring further. # Re-encrypt Available in Classic and VPC Reencrypt the ciphertext with the most recent version of the specified master key. It can only be requested as an AES256 or RSA2048 key type. ## Request This section describes the request format. The method and URI are as follows: | Method | URI | | --- | --- | | POST | - API Gateway request signature v1: /keys/v1/{keyTag}/reencrypt - API Gateway request signature v2: /keys/v2/{keyTag}/reencrypt | ### Request headers For information about the headers common to all Key Management Service APIs, see [Key Management Service request headers](/docs/en/security-kms#%EC%9A%94%EC%B2%AD%ED%97%A4%EB%8D%941). ### Request path parameters You can use the following path parameters with your request: | Field | Type | Required | Description | | --- | --- | --- | --- | | `keyTag` | String | Required | Key tag - Unique identifier for the key derived from the key name. - See [Get key list](/docs/en/security-kms2-key-list). - Use to request encryption or decryption with REST APIs. - Key tags are not treated as confidential information. | ### Request body You can include the following data in the body of your request: | Field | Type | Required | Description | | --- | --- | --- | --- | | `ciphertext` | String or Array[String] | Required | String data created by encrypting a plaintext | | `context` | String | Conditional | Base64-encoded string data - Required when using keys with convergent encryption. - Can be up to 50 bytes long. - Always generate the same ciphertext, even when encrypting the same data multiple times. | ### Request example The request example is as follows: - Request API Gateway request signature v1 and `ciphertext` as String type ``` curl --location --request POST 'https://kms.apigw.ntruss.com/keys/v1/a1b2c3d4e5f6g7h8i9j0k1l2m3n4o5p6q7r8s9t0u1v2w3x4y5z6/reencrypt' \ --header 'x-ncp-apigw-timestamp: {Timestamp}' \ --header 'x-ncp-apigw-api-key: {API Gateway API Key}' \ --header 'x-ncp-iam-access-key: {Sub Account Access Key}' \ --header 'x-ncp-apigw-signature-v1: {API Gateway Signature}' \ --data '{ "ciphertext": "{CIPHERTEXT}", "context": "{BASE64_CONTEXT}" }' ``` - Request API Gateway request signature v2 and `ciphertext` as Array[String] type ``` curl --location --request POST 'https://kms.apigw.ntruss.com/keys/v2/a1b2c3d4e5f6g7h8i9j0k1l2m3n4o5p6q7r8s9t0u1v2w3x4y5z6/reencrypt' \ --header 'x-ncp-apigw-timestamp: {Timestamp}' \ --header 'x-ncp-iam-access-key: {Sub Account Access Key}' \ --header 'x-ncp-apigw-signature-v2: {API Gateway Signature}' \ --data '{ "ciphertext": ["{CIPHERTEXT_1}", "{CIPHERTEXT_2}", "{CIPHERTEXT_3}"], "context": "{BASE64_CONTEXT}" }' ``` ## Response This section describes the response format. ### Response body The response body includes the following data: | Field | Type | Required | Description | | --- | --- | --- | --- | | `code` | String | - | Success or Failure | | `msg` | String | - | Description of the response code (`code`) - Display an empty value ("") on request success (`SUCCESS`). | | `data` | Object | - | Response result | | `data.newCiphertext` | String or Array[String] | - | String data representing the `ciphertext` re-encrypted using the latest version of the specified master key | ### Response status codes For information about the HTTP status codes common to all Key Management Service APIs, see [Key Management Service response status codes](/docs/en/security-kms#%EC%9D%91%EB%8B%B5%EC%83%81%ED%83%9C%EC%BD%94%EB%93%9C1). ### Response example The response example is as follows: - Request `ciphertext` as String type ``` { "code": "SUCCESS", "msg": "", "data": { "newCiphertext": "{CIPHERTEXT_NEW}" } } ``` - Request `ciphertext` as Array[String] type ``` { "code": "SUCCESS", "msg": "", "data": { "newCiphertext": [ "{CIPHERTEXT_NEW_1}", "{CIPHERTEXT_NEW_2}", "{CIPHERTEXT_NEW_3}" ] } } ```