How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Livepeer accessControl API

Operations related to access control/signing keys api

Livepeer accessControl API is one of 35 APIs that Livepeer publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Access Control. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 5 operations across 2 paths, and defines 2 schemas. It is described by OpenAPI 3.2.0, at version 1.0.0.

Requests are made against a single base URL, https://livepeer.studio/api.

5 operations 2 paths 2 schemas 1 DELETE2 GET1 PATCH1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0
Base URL
https://livepeer.studio/api
Authentication
HTTP Bearer, HTTP Bearer
Resource Areas
1

Authentication & Security 2

Livepeer accessControl API declares 2 security schemes for authenticating requests. It accepts HTTP bearer tokens (JWT) (apiKey). It accepts HTTP bearer tokens (HTTPBearer). By default, every request must be authenticated.

Paths & Operations 5

Across 2 paths, the API surfaces 5 operations — 1 DELETE, 2 GET, 1 PATCH, 1 POST. Each is listed below with its method, path, parameters, and response codes.

accessControl 5

Operations related to access control/signing keys api

POST
/access-control/signing-key
Create a signing key
createSigningKey → default200
GET
/access-control/signing-key
Retrieves signing keys
getSigningKeys → default200
DELETE
/access-control/signing-key/{keyId}
Delete Signing Key
deleteSigningKey 1 param → default204
GET
/access-control/signing-key/{keyId}
Retrieves a signing key
getSigningKey 1 param → default200
PATCH
/access-control/signing-key/{keyId}
Update a signing key
updateSigningKey 1 param body → default204

Schemas 2

The contract defines 2 schemas that model the data the API accepts and returns. The most detailed are signing-key (8 properties), error (1 property). Each schema is shown below with its type and property counts.

signing-key
object
8 properties 1 required
error
object
1 property

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

livepeer-accesscontrol-api-openapi.yml Raw ↑

Other APIs Livepeer publishes across the network.

Livepeer Studio REST API
Livepeer Streams API
Livepeer Assets API
Livepeer Multistream Targets API
Livepeer Webhooks API
Livepeer Transcode API
Livepeer Sessions API
Livepeer Playback API
Livepeer Signing Keys API
Livepeer AI Generate API
Livepeer JavaScript/TypeScript SDK
Livepeer Python SDK
Where this information came from

This is an independent, third-party profile of Livepeer accessControl API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.