emnify · API Governance Rules
emnify API Rules
Spectral linting rules defining API design standards and conventions for emnify.
10 Rules
error 3
warn 7
Rule Categories
emnify
Rules
warn
emnify-info-contact
emnify OpenAPI specs must reference the emnify developer support contact.
$.info.contact
warn
emnify-server-uses-cdn-host
emnify REST API uses the cdn.emnify.net host.
$.servers[*].url
warn
emnify-paths-use-api-v1-or-v2
emnify paths are versioned under /api/v1 or /api/v2.
$.paths.*~
warn
emnify-operation-summary-title-case
All operation summaries must use Title Case.
$.paths[*][get,post,put,patch,delete].summary
error
emnify-operation-has-operationid
Every operation must have an operationId.
$.paths[*][get,post,put,patch,delete]
error
emnify-operation-has-tags
Every operation must be tagged with at least one subpackage tag.
$.paths[*][get,post,put,patch,delete]
warn
emnify-operation-tag-prefix
emnify operation tags use the subpackage_* prefix.
$.paths[*][get,post,put,patch,delete].tags[*]
warn
emnify-bearer-auth-required
emnify operations require the BearerAuth security scheme (JWT). Allow opt-out only for /api/v1/authenticate.
$.components.securitySchemes
warn
emnify-paths-use-snake-case
emnify path segments use snake_case (not kebab-case).
$.paths.*~
error
emnify-operation-has-2xx-response
Every operation must define at least one 2xx response.
$.paths[*][get,post,put,patch,delete].responses