University of Pennsylvania · API Governance Rules
University of Pennsylvania API Rules
Spectral linting rules defining API design standards and conventions for University of Pennsylvania.
6 Rules
error 2
warn 3
Rule Categories
upenn
Rules
error
upenn-info-title
API must declare a title.
$.info
warn
upenn-operation-description
Every operation should have a description (observed throughout the Penn Courses API).
$.paths[*][get,post,put,patch,delete]
warn
upenn-operation-tags
Operations should be tagged (e.g. Plan, Review, Alert, Degree, Base).
$.paths[*][get,post,put,patch,delete]
warn
upenn-path-kebab-or-snake
Path segments use lowercase letters, digits, dashes, underscores, or path params (observed convention, e.g. /api/review/course_plots).
$.paths[*]~
hint
upenn-course-code-param
Course code path params should be documented (e.g. course_code, full_code).
$.paths[*].*.parameters[?(@.in=='path')]
error
upenn-success-response
GET operations must define a 200 response.
$.paths[*].get.responses