--- title: "Decrypt" slug: "security-kms-decrypt" tags: ["Key Management Service", "KMS"] updated: 2026-10-08T04:20:22Z published: 2026-10-08T04:20:22Z canonical: "api.ncloud-docs.com/security-kms-decrypt" --- > ## 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. # Decrypt Available in Classic and VPC Decrypt the ciphertext encrypted with a key. It can only be requested as an AES256 or RSA2048 key type. Caution The data encrypted with the master key and returned consists of `KMS prefix + ciphertext`. The KMS prefix is composed of `ncpkms:version information`, and it must be specified exactly with the ciphertext because it will be decrypted with the key version specified in the decryption request. If the KMS prefix is incorrect, it will not be decrypted correctly, so be sure to manage the encryption in the form it is returned, with no arbitrary removals or manipulations. ``` ncpkms:v1:XjsPWPjqPrBi1N2DupSiSbX/ATkGmKA ---------- ------------------------------- KMS prefix ciphertext ``` ## 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}/decrypt - API Gateway request signature v2: /keys/v2/{keyTag}/decrypt | ### Request headers For information about the request 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 - The `context` parameter value used when encrypting data with a key that has convergent encryption applied is required. | ### 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/decrypt' \ --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/decrypt' \ --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.plaintext` | String or Array[String] | - | Decrypted string data - Base64-encoded string data before encryption | ### Response status codes For information about the response 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": { "plaintext": "{BASE64_PLAINTEXT}" } } ``` - Request `ciphertext` as Array[String] type ``` { "code": "SUCCESS", "msg": "", "data": { "plaintext": [ "{BASE64_PLAINTEXT_1}", "{BASE64_PLAINTEXT_2}", "{BASE64_PLAINTEXT_3}" ] } } ``` ### Decrypt data encrypted with RSA2048 public key For RSA2048, even data encrypted directly with a public key without calling the NCP KMS API can be decrypted using this API, provided it was encrypted under the same conditions specified in [Encrypt](/docs/en/security-kms-encrypt#%EC%95%94%ED%98%B8%ED%99%94%ED%8C%8C%EB%9D%BC%EB%AF%B8%ED%84%B0). When requesting decryption, you must Base64-encode the RSA ciphertext, append the KMS ciphertext identifier prefix, and pass it as `ciphertext`. ``` ncpkms:v{key version}:{Base64 (RSA ciphertext)} ``` For public key query and encryption examples, see [Get public key](/docs/en/security-kms2-token-public-key#%EA%B3%B5%EA%B0%9C%ED%82%A4%EB%A1%9C%EC%95%94%ED%98%B8%ED%99%94). Note Since KMS decrypts the data using the same parameters used for encryption, there is no need to specify separate algorithm parameters. If you want to decrypt data that was encrypted directly with the public key, you must match the parameters exactly. For more information, see the encryption parameters in [Encrypt](/docs/en/security-kms-encrypt#%EC%95%94%ED%98%B8%ED%99%94%ED%8C%8C%EB%9D%BC%EB%AF%B8%ED%84%B0).