Register a communication key

POST

/tenants/{tenant_id}/communication-keys

Communication keys sign and verify license tokens. The tenant's
backend uses the private key to sign tokens; the License Acquisition
service uses the public key (HMAC: same key) to verify.

For HS256 keys, the secret is returned ONCE on creation and must be
stored by the caller. For RS256/ES256, the caller may either upload
a public key or have the service generate a keypair.

Request

Authorization

Bearer Token

Provide your bearer token in the

Authorization

header when making requests to protected resources.

Example:

Authorization: Bearer ********************

Path Params

Body Params application/jsonRequired

Examples

Responses

🟢201

application/json

Key registered.

Bodyapplication/json

Request Example

Shell

JavaScript

Java

Swift

curl --location '/tenants//communication-keys' \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '{
    "name": "Production signing key 2026",
    "algorithm": "RS256",
    "generate_keypair": true
}'

Response Example

{
    "id": "ck_01HXYZ...",
    "name": "string",
    "algorithm": "HS256",
    "public_key": "string",
    "secret": "string",
    "kid": "string",
    "status": "active",
    "created_at": "2019-08-24T14:15:22.123Z",
    "expires_at": "2019-08-24T14:15:22.123Z"
}

Modified at 2026-05-16 06:35:55

Delete tenant (soft delete)

List communication keys