Software AG · API Governance Rules
Software AG API Rules
Spectral linting rules defining API design standards and conventions for Software AG.
12 Rules
error 4
warn 6
info 2
Rule Categories
webmethods
Rules
warn
webmethods-api-naming-convention
API names must use camelCase format consistent with webMethods conventions
$.paths[*][*].operationId
error
webmethods-require-operation-id
All operations must have an operationId for code generation
$.paths[*][*]
error
webmethods-require-summary
All operations must have a summary for developer portal display
$.paths[*][*]
warn
webmethods-require-tags
All operations must be tagged for Developer Portal categorization
$.paths[*][*]
info
webmethods-api-id-path-parameter
Resource-specific paths must use {apiId} as the primary identifier
$.paths
error
webmethods-require-response-200
GET operations must define a 200 response
$.paths[*].get
warn
webmethods-require-response-content
Successful responses should define a content schema
$.paths[*][*].responses.200
warn
webmethods-security-required
All operations should reference security schemes (Basic Auth required)
$.paths[*][*]
info
webmethods-rest-v1-prefix
API Gateway REST paths use the /rest/apigateway base path
$.servers[*].url
warn
webmethods-parameter-descriptions
All parameters should include descriptions for Developer Portal display
$.paths[*][*].parameters[*]
error
webmethods-request-body-content-type
Request bodies must specify a content type
$.paths[*][*].requestBody
warn
webmethods-schema-properties
Schema objects should define their properties
$.components.schemas[*]