US House of Representatives · API Governance Rules
US House of Representatives API Rules
Spectral linting rules defining API design standards and conventions for US House of Representatives.
11 Rules
error 1
warn 6
info 4
Rule Categories
congress
Rules
warn
congress-operation-ids-camel-case
Operation IDs must use camelCase naming
$.paths[*][*].operationId
error
congress-operations-have-summaries
All operations must have a summary
$.paths[*][get,post,put,patch,delete]
warn
congress-operations-have-tags
All operations should be tagged for grouping
$.paths[*][get,post,put,patch,delete]
warn
congress-response-200-defined
All GET operations should define a 200 response
$.paths[*][get]
info
congress-v3-path-prefix
All paths should use the v3 versioning format
$.servers[*].url
info
congress-format-param-documented
Format parameters should list valid values
$.paths[*][*].parameters[?(@.name == 'format')]
info
congress-limit-param-max
Limit parameters should specify the maximum allowed value
$.paths[*][*].parameters[?(@.name == 'limit')]
warn
congress-security-scheme-defined
API should define authentication/security scheme
$.components.securitySchemes
warn
congress-info-contact-present
API should include contact information
$.info
warn
congress-tags-title-case
Tags must use Title Case naming
$.tags[*].name
info
congress-path-versioned
API paths should not hardcode version numbers
$.paths