LIlivepeer
accessControl

Create a signing key

Changed on

The publicKey is a representation of the public key, encoded as base 64 and is passed as a string, and the privateKey is displayed only on creation. This is the only moment where the client can save the private key, otherwise it will be lost. Remember to decode your string when signing JWTs. Up to 10 signing keys can be generated, after that you must delete at least one signing key to create a new one.

post/access-control/signing-key

Request

  • Base URL
    https://livepeer.studio/api
  • URL
    https://livepeer.studio/api/access-control/signing-key
  • Auth
    HTTP bearer

Response

Success

idstring
namestring

Name of the signing key

userIdstring
createdAtnumber

Timestamp (in milliseconds) at which the signing-key was created

lastSeennumber

Timestamp (in milliseconds) at which the signing-key was last used

publicKeystring required
disabledboolean

Disable the signing key to allow rotation safely

projectIdstring

The ID of the project

Example response

{
  "id": "78df0075-b5f3-4683-a618-1086faca35dc",
  "name": "key1",
  "userId": "78df0075-b5f3-4683-a618-1086faca35dc",
  "createdAt": 1587667174725,
  "lastSeen": 1587667174725,
  "projectId": "aac12556-4d65-4d34-9fb"
}

Changes