emnify · API Governance Rules

emnify API Rules

Spectral linting rules defining API design standards and conventions for emnify.

10 Rules error 3 warn 7
View Rules File View on GitHub

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

Spectral Ruleset

Raw ↑
extends:
  - spectral:oas

functions: []

rules:
  emnify-info-contact:
    description: emnify OpenAPI specs must reference the emnify developer support contact.
    message: 'info.contact.url should reference https://docs.emnify.com/developers'
    severity: warn
    given: $.info.contact
    then:
      - field: url
        function: pattern
        functionOptions:
          match: 'docs\.emnify\.com/developers'

  emnify-server-uses-cdn-host:
    description: emnify REST API uses the cdn.emnify.net host.
    message: 'servers[*].url should be https://cdn.emnify.net'
    severity: warn
    given: $.servers[*].url
    then:
      function: pattern
      functionOptions:
        match: 'cdn\.emnify\.net'

  emnify-paths-use-api-v1-or-v2:
    description: emnify paths are versioned under /api/v1 or /api/v2.
    message: 'Path should start with /api/v1 or /api/v2'
    severity: warn
    given: $.paths.*~
    then:
      function: pattern
      functionOptions:
        match: '^/api/v[12]/'

  emnify-operation-summary-title-case:
    description: All operation summaries must use Title Case.
    message: 'Summary should use Title Case (first letter of each major word capitalized).'
    severity: warn
    given: $.paths[*][get,post,put,patch,delete].summary
    then:
      function: pattern
      functionOptions:
        match: '^([A-Z][a-zA-Z0-9]*)(\s+[A-Za-z0-9][a-zA-Z0-9]*)*$'

  emnify-operation-has-operationid:
    description: Every operation must have an operationId.
    message: 'operationId is required.'
    severity: error
    given: $.paths[*][get,post,put,patch,delete]
    then:
      field: operationId
      function: truthy

  emnify-operation-has-tags:
    description: Every operation must be tagged with at least one subpackage tag.
    severity: error
    given: $.paths[*][get,post,put,patch,delete]
    then:
      field: tags
      function: truthy

  emnify-operation-tag-prefix:
    description: emnify operation tags use the subpackage_* prefix.
    message: 'Tag should start with subpackage_'
    severity: warn
    given: $.paths[*][get,post,put,patch,delete].tags[*]
    then:
      function: pattern
      functionOptions:
        match: '^subpackage_'

  emnify-bearer-auth-required:
    description: emnify operations require the BearerAuth security scheme (JWT). Allow opt-out only for /api/v1/authenticate.
    severity: warn
    given: $.components.securitySchemes
    then:
      field: BearerAuth
      function: truthy

  emnify-paths-use-snake-case:
    description: emnify path segments use snake_case (not kebab-case).
    message: 'Path segments should use snake_case.'
    severity: warn
    given: $.paths.*~
    then:
      function: pattern
      functionOptions:
        match: '^(/[a-z0-9_{}-]+)+$'

  emnify-operation-has-2xx-response:
    description: Every operation must define at least one 2xx response.
    severity: error
    given: $.paths[*][get,post,put,patch,delete].responses
    then:
      function: schema
      functionOptions:
        schema:
          type: object
          patternProperties:
            '^2\d\d$': {}
          minProperties: 1

Work with this as data

Every ruleset here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for spectral rules

4 MCP tools reach this
  • find_rulesBrowse and filter every ruleset in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This ruleset
curl "https://apis.io/api/v1/rules/emnify-rules"
All spectral rules
curl "https://apis.io/api/v1/rules?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.