BigID · API Governance Rules
BigID API Rules
Spectral linting rules defining API design standards and conventions for BigID.
6 Rules
error 1
warn 4
info 1
Rule Categories
bigid
Rules
warn
bigid-operation-summary-title-case
Operation summaries should be Title Case, matching BigID developer-portal style.
$.paths[*][get,post,put,patch,delete].summary
error
bigid-operation-must-have-operation-id
All operations must declare an operationId so SDK generators and Naftiko bindings can resolve them.
$.paths[*][get,post,put,patch,delete]
warn
bigid-paths-kebab-or-snake-case
BigID API paths use either kebab-case or snake_case; mixed casing inside a segment is discouraged.
$.paths[*]~
warn
bigid-bearer-auth-declared
Each API must declare a Bearer JWT security scheme reflecting BigID's auth_token / systemToken pattern.
$.components.securitySchemes
warn
bigid-tags-required
Every operation should be tagged so the BigID developer portal can group it.
$.paths[*][get,post,put,patch,delete]
info
bigid-server-baseurl-includes-api-v1
BigID REST APIs are versioned under /api/v1; servers should reflect that prefix.
$.servers[*].url