Skip to content

Publishes an additional signing key. It signs nothing until it is promoted, so this is the safe first step of a rotation: publish, ship a build pinning both keys, then promote.

POST
/api/v1/provision/admin/providers/license-signing-keys
curl --request POST \
--url https://example.com/api/v1/provision/admin/providers/license-signing-keys \
--header 'Content-Type: application/json' \
--data '{ "name": "example", "expirationDate": "2026-04-15T12:00:00Z" }'
One of:
null
Examplegenerated
{
"name": "example",
"expirationDate": "2026-04-15T12:00:00Z"
}

OK

Public half of the provider’s license-signing keypair. Vendors embed string LicenseSigningKeyDto.PublicKey in their application so the license consumer SDK can verify license token signatures offline.

object
keyId
string
publicKey

Base64-encoded (PKCS#1) RSA public key.

string
isDefault

Whether new licenses and offline envelopes are currently signed with this key.

boolean
createdAt

When the key was published.

string format: date-time
expirationDate

When the key stops verifying anything it signed, if an expiry was set.

null | string format: date-time
name

Operator-facing label, to tell keys apart during a rotation.

string

Forbidden

object
type
null | string
title
null | string
status
null | integer | string format: int32
/^-?(?:0|[1-9]\d*)$/
detail
null | string
instance
null | string

Not Found

object
type
null | string
title
null | string
status
null | integer | string format: int32
/^-?(?:0|[1-9]\d*)$/
detail
null | string
instance
null | string