Bringg · API Governance Rules
Bringg API Rules
Spectral linting rules defining API design standards and conventions for Bringg.
5 Rules
error 2
warn 3
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.
Rule Categories
bringg
Rules
error
bringg-operation-summary-required
Every operation must have a summary in Title Case.
$.paths.*[get,post,put,patch,delete]
warn
bringg-operation-id-camelcase
operationId must be camelCase.
$.paths.*[get,post,put,patch,delete].operationId
error
bringg-oauth-required
All operations must be secured with OAuth 2.0 Client Credentials.
$
warn
bringg-region-server
At least one region-specific Bringg server URL must be declared.
$.servers
warn
bringg-info-contact
info.contact must be present with developer support URL.
$.info
Spectral Ruleset
Work with this as data
Every ruleset here is available over the APIs.io API and to AI agents over MCP.