Ryder System · API Governance Rules

Ryder System API Rules

Spectral linting rules defining API design standards and conventions for Ryder System.

7 Rules error 3 warn 3 info 1
View Rules File View on GitHub

Rule Categories

ryder

Rules

error
ryder-api-key-auth
Ryder APIs use API key authentication via Ocp-Apim-Subscription-Key header
$.components.securitySchemes
warn
ryder-operation-id-camel-case
All Ryder operationIds should use camelCase
$.paths[*][*].operationId
warn
ryder-tags-title-case
All tags must use Title Case
$.paths[*][*].tags[*]
warn
ryder-summaries-title-case
Operation summaries must use Title Case
$.paths[*][*].summary
error
ryder-response-200-required
All operations must have a 200 or 201 success response
$.paths[*][get,post,put,patch,delete].responses
info
ryder-pagination-page-params
List operations should support page/pageSize pagination
$.paths[*].get
error
ryder-path-params-required
Path parameters must be marked as required
$.paths[*][*].parameters[?(@.in == 'path')]

Spectral Ruleset

Raw ↑
extends: spectral:oas
rules:
  ryder-api-key-auth:
    description: Ryder APIs use API key authentication via Ocp-Apim-Subscription-Key header
    message: "API must define Ocp-Apim-Subscription-Key apiKey security scheme"
    severity: error
    given: "$.components.securitySchemes"
    then:
      function: truthy

  ryder-operation-id-camel-case:
    description: All Ryder operationIds should use camelCase
    message: "OperationId '{{value}}' should use camelCase naming"
    severity: warn
    given: "$.paths[*][*].operationId"
    then:
      function: pattern
      functionOptions:
        match: "^[a-z][a-zA-Z0-9]*$"

  ryder-tags-title-case:
    description: All tags must use Title Case
    message: "Tag '{{value}}' should use Title Case"
    severity: warn
    given: "$.paths[*][*].tags[*]"
    then:
      function: pattern
      functionOptions:
        match: "^[A-Z][a-zA-Z0-9 &-]*$"

  ryder-summaries-title-case:
    description: Operation summaries must use Title Case
    message: "Summary '{{value}}' should use Title Case"
    severity: warn
    given: "$.paths[*][*].summary"
    then:
      function: pattern
      functionOptions:
        match: "^[A-Z][a-zA-Z0-9 &-]*$"

  ryder-response-200-required:
    description: All operations must have a 200 or 201 success response
    message: "Operation '{{description}}' is missing a success response"
    severity: error
    given: "$.paths[*][get,post,put,patch,delete].responses"
    then:
      function: schema
      functionOptions:
        schema:
          type: object
          anyOf:
            - required: ["200"]
            - required: ["201"]

  ryder-pagination-page-params:
    description: List operations should support page/pageSize pagination
    message: "List operation should support page and pageSize parameters"
    severity: info
    given: "$.paths[*].get"
    then:
      field: parameters
      function: truthy

  ryder-path-params-required:
    description: Path parameters must be marked as required
    message: "Path parameter '{{value}}' must be marked as required: true"
    severity: error
    given: "$.paths[*][*].parameters[?(@.in == 'path')]"
    then:
      field: required
      function: truthy

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/ryder-spectral-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.