MyCase · API Governance Rules
MyCase API Rules
Spectral linting rules defining API design standards and conventions for MyCase.
5 Rules
error 1
warn 4
Authorship not recorded
No authorship marker is recorded for this file. It is not presented as the provider's; it was most likely written by an API Evangelist pass before outputs were stamped.
Rule Categories
mycase
Rules
warn
mycase-operation-summary-title-case
Operation summaries must use Title Case (matches MyCase's Stoplight summaries).
$.paths[*][get,post,put,patch,delete].summary
warn
mycase-operation-id-camel-case
Operation IDs must be lowerCamelCase.
$.paths[*][get,post,put,patch,delete].operationId
warn
mycase-path-snake-case
Path segments (other than path parameters) must be snake_case to match MyCase conventions (case_stages, client_relationships, documents_folder).
$.paths
error
mycase-tag-defined
Every operation must include at least one tag.
$.paths[*][get,post,put,patch,delete]
warn
mycase-bearer-security
All operations must require bearer auth (MyCase Open API is gated).
$.paths[*][get,post,put,patch,delete]
Spectral Ruleset
Work with this as data
Every ruleset here is available over the APIs.io API and to AI agents over MCP.