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
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