{ "opencollection": "1.0.0", "info": { "name": "Vault Key Management Kms Crypto API", "version": "release" }, "items": [ { "info": { "name": "kmsCrypto", "type": "folder" }, "items": [ { "info": { "name": "Decrypt", "type": "http" }, "http": { "method": "POST", "url": "/20180608/decrypt", "headers": [ { "name": "opc-request-id", "value": "" } ], "body": { "type": "json", "data": "{}" } }, "docs": "Decrypts data using the given [DecryptDataDetails](/api/#/en/key/latest/datatypes/DecryptDataDetails) resource.\n" }, { "info": { "name": "Encrypt", "type": "http" }, "http": { "method": "POST", "url": "/20180608/encrypt", "headers": [ { "name": "opc-request-id", "value": "" } ], "body": { "type": "json", "data": "{}" } }, "docs": "Encrypts data using the given [EncryptDataDetails](/api/#/en/key/latest/datatypes/EncryptDataDetails) resource.\nPlaintext included in the example request is a base64-encoded value of a UTF-8 string.\n" }, { "info": { "name": "Exports a master encryption key.", "type": "http" }, "http": { "method": "POST", "url": "/20180608/exportKey", "body": { "type": "json", "data": "{}" } }, "docs": "Exports a specific version of a master encryption key according to the details of the request. For their protection,\nkeys that you create and store on a hardware security module (HSM) can never leave the HSM. You can only export keys\nstored on the server. For export, the key version is encrypted by an RSA public key that you provide.\nThis operation is not supported for keys having protection mode `EXTERNAL`.\n" }, { "info": { "name": "GenerateDataEncryptionKey", "type": "http" }, "http": { "method": "POST", "url": "/20180608/generateDataEncryptionKey", "headers": [ { "name": "opc-request-id", "value": "" } ], "body": { "type": "json", "data": "{}" } }, "docs": "Generates a key that you can use to encrypt or decrypt data.\n" }, { "info": { "name": "Signs data by using the given SignDataDetails resource.", "type": "http" }, "http": { "method": "POST", "url": "/20180608/sign", "headers": [ { "name": "opc-request-id", "value": "" } ], "body": { "type": "json", "data": "{}" } }, "docs": "Creates a digital signature for a message or message digest by using the private key of a public-private key pair,\nalso known as an asymmetric key. To verify the generated signature, you can use the [Verify](/api/#/en/key/latest/VerifiedData/Verify)\noperation. Or, if you want to validate the signature outside of the service, you can do so by using the public key of the same asymmetric key.\nThis operation is not supported for keys having protection mode `EXTERNAL`.\n" }, { "info": { "name": "Verifies signed data by using the given VerifyDataDetails resource.", "type": "http" }, "http": { "method": "POST", "url": "/20180608/verify", "headers": [ { "name": "opc-request-id", "value": "" } ], "body": { "type": "json", "data": "{}" } }, "docs": "Verifies a digital signature that was generated by the [Sign](/api/#/en/key/latest/SignedData/Sign) operation\nby using the public key of the same asymmetric key that was used to sign the data. If you want to validate the\ndigital signature outside of the service, you can do so by using the public key of the asymmetric key.\nThis operation is not supported for keys having protection mode `EXTERNAL`.\n" } ] } ], "bundled": true }