University of Sussex · API Governance Rules
University of Sussex API Rules
Spectral linting rules defining API design standards and conventions for University of Sussex.
6 Rules
warn 3
info 3
Rule Categories
sussex
Rules
warn
sussex-info-contact
API info should include a contact for support.
$.info
warn
sussex-servers-figshare
Server URL should point at the Figshare v2 API base.
$.servers[*].url
info
sussex-operation-id-snake-case
Figshare operationIds use snake_case (e.g. articles_list).
$.paths[*][get,post,put,delete,patch].operationId
info
sussex-article-identifier-fields
Article-like response schemas should expose id, doi, and url identifiers.
$.components.schemas.Article.properties
warn
sussex-get-has-200
GET operations should define a 200 response.
$.paths[*].get.responses
info
sussex-tags-defined
Operations should be tagged for navigability (articles, collections, projects, etc.).
$.paths[*][get,post,put,delete,patch]