TIBCO · API Governance Rules

TIBCO API Rules

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

13 Rules error 4 warn 5 info 4
View Rules File View on GitHub

Rule Categories

tibco

Rules

warn
tibco-operation-ids-camel-case
Operation IDs must use camelCase
$.paths[*][*].operationId
warn
tibco-tags-title-case
All tags must use Title Case
$.tags[*].name
warn
tibco-paths-kebab-case
Path segments must use kebab-case or camelCase only
$.paths[*]~
error
tibco-security-defined
All operations must have security requirements
$.paths[*][get,post,put,patch,delete]
warn
tibco-responses-200-on-get
GET operations must have a 200 response
$.paths[*].get
info
tibco-responses-401-defined
Protected operations should document 401 response
$.paths[*][get,post,put,delete]
error
tibco-request-body-json-schema
POST/PUT request bodies must define a JSON schema
$.paths[*][post,put].requestBody.content.application/json
error
tibco-servers-https-only
All server URLs must use HTTPS
$.servers[*].url
error
tibco-info-version-defined
API info must specify a version
$.info
warn
tibco-info-contact-defined
API info must include contact information
$.info
info
tibco-component-schemas-use-refs
Response schemas should use $ref to component schemas
$.paths[*][*].responses.200.content[*].schema
info
tibco-ids-in-path-params
Resource identifier path parameters should end with 'Id'
$.paths[*][*].parameters[?(@.in == 'path')].name
info
tibco-delete-returns-204
DELETE operations should return 204 No Content
$.paths[*].delete

Spectral Ruleset

Raw ↑
extends:
  - spectral:oas

rules:
  tibco-operation-ids-camel-case:
    description: Operation IDs must use camelCase
    severity: warn
    given: "$.paths[*][*].operationId"
    then:
      function: pattern
      functionOptions:
        match: "^[a-z][a-zA-Z0-9]+$"

  tibco-tags-title-case:
    description: All tags must use Title Case
    severity: warn
    given: "$.tags[*].name"
    then:
      function: pattern
      functionOptions:
        match: "^[A-Z][a-zA-Z0-9 &-]+$"

  tibco-paths-kebab-case:
    description: Path segments must use kebab-case or camelCase only
    severity: warn
    given: "$.paths[*]~"
    then:
      function: pattern
      functionOptions:
        match: "^(/[a-zA-Z][a-zA-Z0-9-]*|/\\{[a-zA-Z][a-zA-Z0-9]+\\})*$"

  tibco-security-defined:
    description: All operations must have security requirements
    severity: error
    given: "$.paths[*][get,post,put,patch,delete]"
    then:
      field: security
      function: defined

  tibco-responses-200-on-get:
    description: GET operations must have a 200 response
    severity: warn
    given: "$.paths[*].get"
    then:
      field: responses.200
      function: defined

  tibco-responses-401-defined:
    description: Protected operations should document 401 response
    severity: info
    given: "$.paths[*][get,post,put,delete]"
    then:
      field: responses.401
      function: defined

  tibco-request-body-json-schema:
    description: POST/PUT request bodies must define a JSON schema
    severity: error
    given: "$.paths[*][post,put].requestBody.content.application/json"
    then:
      field: schema
      function: defined

  tibco-servers-https-only:
    description: All server URLs must use HTTPS
    severity: error
    given: "$.servers[*].url"
    then:
      function: pattern
      functionOptions:
        match: "^https://"

  tibco-info-version-defined:
    description: API info must specify a version
    severity: error
    given: "$.info"
    then:
      field: version
      function: defined

  tibco-info-contact-defined:
    description: API info must include contact information
    severity: warn
    given: "$.info"
    then:
      field: contact
      function: defined

  tibco-component-schemas-use-refs:
    description: Response schemas should use $ref to component schemas
    severity: info
    given: "$.paths[*][*].responses.200.content[*].schema"
    then:
      function: schema
      functionOptions:
        schema:
          oneOf:
            - required: ["$ref"]
            - required: ["type"]

  tibco-ids-in-path-params:
    description: Resource identifier path parameters should end with 'Id'
    severity: info
    given: "$.paths[*][*].parameters[?(@.in == 'path')].name"
    then:
      function: pattern
      functionOptions:
        match: "^.*[Ii]d$"

  tibco-delete-returns-204:
    description: DELETE operations should return 204 No Content
    severity: info
    given: "$.paths[*].delete"
    then:
      field: responses.204
      function: defined

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/tibco-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.