University of Warwick · API Governance Rules
University of Warwick API Rules
Spectral linting rules defining API design standards and conventions for University of Warwick.
9 Rules
error 1
warn 6
info 2
Rule Categories
envelope
info
operation
property
server
Rules
warn
operation-operationId-exists
Every operation should declare an operationId (100% in this API).
$.paths[*][get,post,put,delete,patch]
warn
operation-operationId-casing
operationId should be camelCase (this API's convention, 15/15).
$.paths[*][get,post,put,delete,patch].operationId
warn
operation-summary-exists
Every operation should declare a summary (100% in this API).
$.paths[*][get,post,put,delete,patch]
warn
operation-tag-exists
Every operation should be tagged (100% in this API).
$.paths[*][get,post,put,delete,patch]
info
property-name-casing
Schema properties should be camelCase (34/34 in this API).
$.components.schemas..properties
info
envelope-declares-success
Every Tabula response schema is wrapped in the success/status envelope. Response schemas should compose it rather than returning a bare payload.
$.components.schemas.Envelope.properties
error
server-is-warwick-operated
Operator guard. Every server URL in this provider's contracts must sit under warwick.ac.uk. A server on a vendor host means the contract belongs in the vendor's own repository, not this institution's — this is the check the June 2026 university cohort did not have.
$.servers[*].url
warn
info-contact-exists
info.contact should name the operating team.
$.info
warn
info-description-exists
info.description should state what the API is and who runs it.
$.info