Generate Key Pair
POST/api/v1/key/generate
Generate a dedicated Splitit key pair that you can use to PGP-encrypt traffic sent to Splitit or to verify that a message coming from Splitit is authentic (RSA). In the first scenario, Splitit securely holds the private key half of the pair and you encrypt your outgoing traffic with the public key half. In the second scenario, you use your public key half to verify that Splitit's communication originated at Splitit (Splitit signs with their private key half).
- Use to encrypt your sensitive outgoing traffic to Splitit that requires an additional layer of encryption (MLE)
- Have Splitit sign reports or other sensitive outgoing traffic so you can verify their authenticity
Request
- application/json
Body
required
Given to you by Splitit support, same as Owner in other calls
Possible values: [RSA
, PGP
]
Possible values: [Unknown
, Reports
, Authentication
, MessageLevelEncryption
, CredentialsDownload
, ResponseSignature
]
Responses
- 200
- 400
- 404
- 500
Response Headers
- application/json
- Schema
- Example (from schema)
Schema
{
"UniqueId": "string",
"Key": "string",
"ExpirationUtc": "2024-06-06T16:41:09.086Z",
"Algorithm": "string"
}
Response Headers
- application/json
- Schema
- Example (from schema)
Schema
Error
object
ExtraData
object
{
"TraceId": "string",
"Error": {
"Code": "string",
"Message": "string",
"AdditionalInfo": "string",
"ExtraData": {}
}
}
Response Headers
- application/json
- Schema
- Example (from schema)
Schema
Error
object
ExtraData
object
{
"TraceId": "string",
"Error": {
"Code": "string",
"Message": "string",
"AdditionalInfo": "string",
"ExtraData": {}
}
}
Response Headers
- application/json
- Schema
- Example (from schema)
Schema
Error
object
ExtraData
object
{
"TraceId": "string",
"Error": {
"Code": "string",
"Message": "string",
"AdditionalInfo": "string",
"ExtraData": {}
}
}