Steelcase · API Governance Rules

Steelcase API Rules

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

8 Rules error 2 warn 6
View Rules File View on GitHub

Rule Categories

steelcase

Rules

warn
steelcase-operation-ids-camel-case
Steelcase RoomWizard API operation IDs use camelCase naming convention.
$.paths[*][*].operationId
warn
steelcase-summaries-title-case
All Steelcase RoomWizard API operation summaries must use Title Case.
$.paths[*][*].summary
error
steelcase-tags-required
Every Steelcase API operation must have at least one tag.
$.paths[*][*]
error
steelcase-booking-required-fields
Booking creation requests must include room_id, subject, start_time, and end_time as required fields.
$.components.schemas.BookingCreate
warn
steelcase-date-time-format
All date and time properties in the Steelcase API should use ISO 8601 date-time format.
$.components.schemas[*].properties[?(@ =~ /.*_time$|.*_at$/)]
warn
steelcase-snake-case-properties
Steelcase RoomWizard API properties use snake_case naming convention (e.g., room_id, start_time, booking_id).
$.components.schemas[*].properties
warn
steelcase-status-enum
Booking status should use the standard Steelcase status values.
$.components.schemas.Booking.properties.status.enum
warn
steelcase-responses-json
Steelcase API responses should return application/json content type.
$.paths[*][*].responses['200'].content

Spectral Ruleset

Raw ↑
extends: spectral:oas
rules:
  steelcase-operation-ids-camel-case:
    description: >-
      Steelcase RoomWizard API operation IDs use camelCase naming convention.
    message: "Operation ID '{{value}}' should use camelCase."
    severity: warn
    given: "$.paths[*][*].operationId"
    then:
      function: casing
      functionOptions:
        type: camel

  steelcase-summaries-title-case:
    description: >-
      All Steelcase RoomWizard API operation summaries must use Title Case.
    message: "Summary '{{value}}' should be in Title Case."
    severity: warn
    given: "$.paths[*][*].summary"
    then:
      function: pattern
      functionOptions:
        match: "^[A-Z][a-zA-Z0-9]*(\\s[A-Z][a-zA-Z0-9]*)*$"

  steelcase-tags-required:
    description: >-
      Every Steelcase API operation must have at least one tag.
    message: "Operations must declare at least one tag."
    severity: error
    given: "$.paths[*][*]"
    then:
      field: tags
      function: truthy

  steelcase-booking-required-fields:
    description: >-
      Booking creation requests must include room_id, subject, start_time,
      and end_time as required fields.
    message: >-
      BookingCreate schema must require room_id, subject, start_time,
      and end_time fields.
    severity: error
    given: "$.components.schemas.BookingCreate"
    then:
      field: required
      function: schema
      functionOptions:
        schema:
          type: array
          contains:
            type: string
            enum:
              - room_id
              - subject
              - start_time
              - end_time

  steelcase-date-time-format:
    description: >-
      All date and time properties in the Steelcase API should use
      ISO 8601 date-time format.
    message: >-
      Date/time fields should declare format: date-time for consistency.
    severity: warn
    given: "$.components.schemas[*].properties[?(@ =~ /.*_time$|.*_at$/)]"
    then:
      field: format
      function: enumeration
      functionOptions:
        values:
          - date-time
          - date

  steelcase-snake-case-properties:
    description: >-
      Steelcase RoomWizard API properties use snake_case naming convention
      (e.g., room_id, start_time, booking_id).
    message: "Property '{{property}}' should use snake_case naming."
    severity: warn
    given: "$.components.schemas[*].properties"
    then:
      function: schema
      functionOptions:
        schema:
          type: object
          propertyNames:
            pattern: "^[a-z][a-z0-9]*(_[a-z0-9]+)*$"

  steelcase-status-enum:
    description: >-
      Booking status should use the standard Steelcase status values.
    message: >-
      Booking status must be one of: confirmed, cancelled, in-progress,
      completed.
    severity: warn
    given: "$.components.schemas.Booking.properties.status.enum"
    then:
      function: truthy

  steelcase-responses-json:
    description: >-
      Steelcase API responses should return application/json content type.
    message: "Success responses must include application/json content."
    severity: warn
    given: "$.paths[*][*].responses['200'].content"
    then:
      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/steelcase-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 email required.

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