Restream · API Governance Rules
Restream API Rules
Spectral linting rules defining API design standards and conventions for Restream.
8 Rules
error 4
warn 4
Rule Categories
restream
Rules
error
restream-operation-id-required
All operations must have an operationId for SDK and documentation generation.
$.paths[*][get,post,put,patch,delete]
error
restream-operation-summary-required
All operations must have a summary for developer experience.
$.paths[*][get,post,put,patch,delete]
warn
restream-summary-title-case
Operation summaries must use Title Case per Restream API style.
$.paths[*][get,post,put,patch,delete].summary
error
restream-tags-required
All operations must be tagged for grouping in the developer portal.
$.paths[*][get,post,put,patch,delete]
warn
restream-oauth2-scopes-documented
OAuth2-secured operations must declare required scopes.
$.paths[*][get,post,put,patch,delete].security[*].OAuth2
error
restream-response-200-required
All operations must define a 200/201 success response.
$.paths[*][get,post,put,patch,delete].responses
warn
restream-path-kebab-case
API paths must use kebab-case for multi-word segments.
$.paths[*]~
warn
restream-v2-prefix
All paths must be prefixed with /v2 or use the OAuth token path.
$.paths[*]~