Mux · API Governance Rules
Mux API Rules
Spectral linting rules defining API design standards and conventions for Mux.
9 Rules
warn 9
Rule Categories
mux
Rules
warn
mux-info-contact
API info should include the Mux DevEx contact.
$.info
warn
mux-info-title
API info title must include "Mux".
$.info.title
warn
mux-server-api
At least one server must reference api.mux.com.
$.servers[*].url
warn
mux-video-assets-resource
Mux Video API should expose /video/v1/assets.
$.paths
warn
mux-live-streams-resource
Mux Live Streaming should expose /video/v1/live-streams.
$.paths
warn
mux-data-views-resource
Mux Data API should expose /data/v1/video-views.
$.paths
warn
mux-operation-summary-title-case
All operations should have a Title Case summary.
$.paths[*][*].summary
warn
mux-operation-tags-required
Every operation must declare at least one tag aligning to a Mux product area.
$.paths[*][get,post,put,patch,delete]
warn
mux-security-basic-or-bearer
Mux uses HTTP Basic with Access Token credentials or JWTs; security schemes should be defined.
$.components.securitySchemes