Baxter International · API Governance Rules

Baxter International — baxter rules

Spectral linting rules defining API design standards and conventions for Baxter International.

5 Rules error 3 warn 2
Authorship not recorded No authorship marker is recorded for this file. It is not presented as the provider's; it was most likely written by an API Evangelist pass before outputs were stamped.
View Rules File View on GitHub

Rule Categories

baxter

Rules

error
baxter-auth-required
All Baxter DeviceBridge API operations must use authentication.
$.paths.*.*.security
error
baxter-operation-id-required
All Baxter API operations must have an operationId.
$.paths.*.*
warn
baxter-device-id-documented
Device endpoints should document device identifier parameters.
$.paths[?(@property.match('device'))].*.parameters
error
baxter-patient-id-required
Patient data endpoints should require patient identification.
$.paths[?(@property.match('patient'))].*.parameters
warn
baxter-fhir-content-type
FHIR endpoints should produce FHIR-compliant content types.
$.paths[?(@property.match('fhir'))].*.responses.200.content

Spectral Ruleset

baxter-spectral-rules.yml Raw ↑ 
rules:
  baxter-auth-required:
    description: All Baxter DeviceBridge API operations must use authentication.
    message: Operation must include authentication security requirement.
    severity: error
    given: $.paths.*.*.security
    then:
      function: schema
      functionOptions:
        schema:
          type: array
          minItems: 1

  baxter-operation-id-required:
    description: All Baxter API operations must have an operationId.
    message: Operation is missing operationId.
    severity: error
    given: $.paths.*.*
    then:
      field: operationId
      function: truthy

  baxter-device-id-documented:
    description: Device endpoints should document device identifier parameters.
    message: Device endpoint should document deviceId path or query parameter.
    severity: warn
    given: $.paths[?(@property.match('device'))].*.parameters
    then:
      function: schema
      functionOptions:
        schema:
          type: array
          minItems: 1

  baxter-patient-id-required:
    description: Patient data endpoints should require patient identification.
    message: Patient data endpoint should document patient identifier parameter.
    severity: error
    given: $.paths[?(@property.match('patient'))].*.parameters
    then:
      function: schema
      functionOptions:
        schema:
          type: array
          minItems: 1

  baxter-fhir-content-type:
    description: FHIR endpoints should produce FHIR-compliant content types.
    message: FHIR endpoint should produce application/fhir+json content type.
    severity: warn
    given: $.paths[?(@property.match('fhir'))].*.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/baxter-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.

GitHub Google LinkedIn

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