Datamuse · API Governance Rules
Datamuse API Rules
Spectral linting rules defining API design standards and conventions for Datamuse.
11 Rules
error 5
warn 6
Rule Categories
datamuse
Rules
error
datamuse-operation-id-required
Every operation must have a non-empty operationId.
$.paths[*][get,post,put,patch,delete]
warn
datamuse-operation-id-camel-case
operationId values must be lowerCamelCase.
$.paths[*][get,post,put,patch,delete].operationId
error
datamuse-operation-summary-required
Every operation must have a summary.
$.paths[*][get,post,put,patch,delete]
warn
datamuse-operation-summary-title-case
Operation summaries must use Title Case.
$.paths[*][get,post,put,patch,delete].summary
warn
datamuse-operation-description-required
Every operation must have a description.
$.paths[*][get,post,put,patch,delete]
warn
datamuse-operation-tags-required
Every operation must declare at least one tag.
$.paths[*][get,post,put,patch,delete]
warn
datamuse-query-parameter-naming
Query parameters must be lowercase and use snake_case for compound names (rel_jja, rel_rhy, etc.).
$.paths[*][get].parameters[?(@.in == 'query')].name
error
datamuse-success-response-json
GET operations must return application/json for 200 responses.
$.paths[*][get].responses['200'].content
warn
datamuse-rate-limit-response
GET operations must document a 429 response for the 100k/day rate limit.
$.paths[*][get].responses
error
datamuse-info-version-required
info.version must be declared.
$.info
error
datamuse-server-https-required
All server URLs must use HTTPS.
$.servers[*].url