--- title: "Verify" slug: "security-kms2-verify" updated: 2026-10-08T04:20:39Z published: 2026-10-08T04:20:39Z canonical: "api.ncloud-docs.com/security-kms2-verify" --- > ## 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. # Verify Available in Classic and VPC Compare the signature value against up to 8 KB of signed data and return a verified result. It can only be requested as an RSA2048 or ECDSA key type. ## Request This section describes the request format. The method and URI are as follows: | Method | URI | | --- | --- | | POST | /kms/v1/keys/{keyTag}/verify | ### Request headers For information about the request headers common to all Key Management Service APIs, see the account authentication method in [Key Management Service request headers](/docs/en/security-kms#%EC%9A%94%EC%B2%AD%ED%97%A4%EB%8D%942%EA%B3%84%EC%A0%95%EC%9D%B8%EC%A6%9D). ### 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 | | --- | --- | --- | --- | | `data` | String | Required | Base64-encoded string data used for signing - Maximum 8 KB can be entered. - Enter the same value as the `data` in the [Sign](/docs/en/security-kms2-sign) request. | | `signature` | String | Required | Signature value to compare - Enter the value from the `data.signature` from the [Sign](/docs/en/security-kms2-sign) response. - `ncpkms:v{key version}: {Base64-encoded signature value}` format. - Validation can't be done if only the signature value without the prefix is entered. - Validation is performed using the key version used to generate the signature; validation can't be done if that key version is deactivated. | Note Since KMS verifies using the same parameters as those used to generate the signature, there is no need to specify signature algorithm parameters. If you are validating directly by retrieving the public key, the parameters must match exactly. For details, see the signature parameters in [Sign](/docs/en/security-kms2-sign#%EC%84%9C%EB%AA%85%ED%8C%8C%EB%9D%BC%EB%AF%B8%ED%84%B0). ### Request example The request example is as follows: ``` curl --location --request POST 'https://ocapi.ncloud.com/kms/v1/keys/a1b2c3d4e5f6g7h8i9j0k1l2m3n4o5p6q7r8s9t0u1v2w3x4y5z6/verify' \ --header 'x-ncp-apigw-timestamp: {Timestamp}' \ --header 'x-ncp-iam-access-key: {Access Key}' \ --header 'x-ncp-apigw-signature-v2: {API Gateway Signature}' \ --data '{ "data": "XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX==", "signature": "ncpkms:v1:{BASE64_SIGNATURE}" }' ``` ## 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 | | `data` | Object | - | Response result | | `data.valid` | String | - | Whether the signed data matches the signature value - `true` \| `false` - `true`: Match - `false`: No match | ### 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%9C2). ### Response example The response example is as follows: ``` { "code": "SUCCESS", "data": { "valid": true } } ```