curl --request POST \
--url https://platform.versori.com/api/organisations/v1/organisations/{organisation_id}/keys \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '
{
"name": "<string>"
}
'{
"id": "<string>",
"name": "Organisation Public Key 1",
"publicKey": "<string>",
"privateKey": "<string>",
"createdAt": "2023-01-01T12:00:00Z"
}Create Signing Key
CreateSigningKey creates a new Signing Key for the Organisation.
This API creates a new RSA key pair, storing the public key and returning the private key. The private key must be kept secure and should not be shared publicly as it has the ability to sign JWTs which can be used to authenticate to Versori APIs on behalf of your Organisation (or scoped to a specific End User within Versori Embedded).
If the private key is lost, it cannot be recovered and a new key pair must be generated. In this scenario, it is the Organisation’s responsibility to delete the Signing Key from Versori so that any JWTs signed by the lost key are invalidated.
curl --request POST \
--url https://platform.versori.com/api/organisations/v1/organisations/{organisation_id}/keys \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '
{
"name": "<string>"
}
'{
"id": "<string>",
"name": "Organisation Public Key 1",
"publicKey": "<string>",
"privateKey": "<string>",
"createdAt": "2023-01-01T12:00:00Z"
}Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Path Parameters
Body
Name of the public key.
Response
OK
Unique identifier for the public key.
Name of the public key.
"Organisation Public Key 1"
The public key in PEM format.
The private key in PEM format.
Timestamp when the public key was created.
"2023-01-01T12:00:00Z"