Livepeer · API Governance Rules
Livepeer API Rules
Spectral linting rules defining API design standards and conventions for Livepeer.
11 Rules
error 2
warn 6
info 3
Rule Categories
livepeer
Rules
error
livepeer-operation-id-required
Every Livepeer Studio operation must declare an operationId
$.paths.*[get,post,put,patch,delete]
warn
livepeer-operation-id-camel-case
Livepeer operationIds must use camelCase (createStream, getMultistreamTargets)
$.paths.*[get,post,put,patch,delete]
warn
livepeer-summary-required
Every operation must have a summary
$.paths.*[get,post,put,patch,delete]
info
livepeer-summary-title-case
Summaries should use sentence/title casing with capitalized first word
$.paths.*[get,post,put,patch,delete]
warn
livepeer-tags-required
Every operation must declare at least one tag
$.paths.*[get,post,put,patch,delete]
warn
livepeer-tag-lowercase
Livepeer tags are lowercase (stream, asset, webhook, room, accessControl, generate)
$.paths.*[get,post,put,patch,delete].tags.*
info
livepeer-bearer-auth
Livepeer Studio requires bearer token (apiKey) security
$.components.securitySchemes.apiKey
info
livepeer-path-kebab-case
Paths must use kebab-case (e.g. /access-control/signing-key, /multistream/target, /start-pull)
$.paths
warn
livepeer-no-trailing-slash
Paths should not have trailing slashes
$.paths
warn
livepeer-2xx-response-defined
Every operation must define at least one 2xx response
$.paths.*[get,post,put,patch,delete].responses
error
livepeer-server-https
Server URLs must use HTTPS
$.servers[*].url