POST
/
api
/
v1
/
kms
/
keys
/
{keyId}
/
sign
curl --request POST \
  --url https://us.infisical.com/api/v1/kms/keys/{keyId}/sign \
  --header 'Content-Type: application/json' \
  --data '{
  "signingAlgorithm": "RSASSA_PSS_SHA_512",
  "isDigest": false,
  "data": "<string>"
}'
{
  "signature": "<string>",
  "keyId": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
  "signingAlgorithm": "RSASSA_PSS_SHA_512"
}

Path Parameters

​
keyId
string
required

The ID of the key to sign the data with.

Body

application/json
​
signingAlgorithm
enum<string>
required
Available options:
RSASSA_PSS_SHA_512,
RSASSA_PSS_SHA_384,
RSASSA_PSS_SHA_256,
RSASSA_PKCS1_V1_5_SHA_512,
RSASSA_PKCS1_V1_5_SHA_384,
RSASSA_PKCS1_V1_5_SHA_256,
ECDSA_SHA_512,
ECDSA_SHA_384,
ECDSA_SHA_256
​
data
string
required

The data in string format to be signed (base64 encoded).

​
isDigest
boolean
default:false

Whether the data is already digested or not. Please be aware that if you are passing a digest the algorithm used to create the digest must match the signing algorithm used to sign the digest.

Response

200
application/json
Default Response
​
signature
string
required
​
keyId
string
required
​
signingAlgorithm
enum<string>
required
Available options:
RSASSA_PSS_SHA_512,
RSASSA_PSS_SHA_384,
RSASSA_PSS_SHA_256,
RSASSA_PKCS1_V1_5_SHA_512,
RSASSA_PKCS1_V1_5_SHA_384,
RSASSA_PKCS1_V1_5_SHA_256,
ECDSA_SHA_512,
ECDSA_SHA_384,
ECDSA_SHA_256

Was this page helpful?

Suggest editsRaise issue