HipChat · API Governance Rules
HipChat API Rules
Spectral linting rules defining API design standards and conventions for HipChat.
9 Rules
error 3
warn 4
info 2
Rule Categories
hipchat
Rules
warn
hipchat-tag-titlecase
All tag names must be Title Case (e.g. "Rooms", "OAuth Sessions").
$.tags[*].name
warn
hipchat-summary-titlecase
Operation summaries must be Title Case (e.g. "Get Room Details").
$.paths[*][get,put,post,delete,patch,options,head].summary
error
hipchat-operation-id-camelcase
operationId values must be lowerCamelCase per HipChat client library naming.
$.paths[*][get,put,post,delete,patch].operationId
error
hipchat-sunset-banner
Sunset/lifecycle metadata MUST be present on info for the historical API.
$.info
error
hipchat-sunset-date-set
A sunset date MUST be recorded for the historical API.
$.info
warn
hipchat-server-list-marked-historical
At least one server should be present and marked as historical in the description.
$.servers[*].description
info
hipchat-auth-header-pattern
REST endpoints should declare security via Bearer or auth_token (HipChat conventions).
$.components.securitySchemes
info
hipchat-pagination-params
List operations should expose start-index and max-results parameters.
$.paths[?(@property.match(/^\/(room|user|emoticon)$/))].get.parameters[*].name
warn
hipchat-room-path-uses-id-or-name
Room endpoints should accept the id_or_name path parameter convention.
$.paths[?(@property.match(/^\/room\//))]