Bright Data · API Governance Rules
Bright Data API Rules
Spectral linting rules defining API design standards and conventions for Bright Data.
8 Rules
error 3
warn 5
Rule Categories
bright
Rules
error
bright-data-info-contact
Bright Data specs must publish contact info.
$.info.contact
warn
bright-data-bearer-auth
Bright Data REST APIs authenticate with a Bearer API token.
$.components.securitySchemes
warn
bright-data-server-api-host
Bright Data production server MUST be https://api.brightdata.com (Proxy Manager uses localhost:22999).
$.servers[*].url
warn
bright-data-operation-summary-title-case
Operation summaries should use Title Case.
$.paths[*][get,post,put,delete,patch].summary
error
bright-data-operation-tags-required
Every Bright Data operation must declare at least one tag.
$.paths[*][get,post,put,delete,patch]
warn
bright-data-snapshot-id-naming
Snapshot identifiers MUST use snake_case `snapshot_id`.
$.paths[?(@property ~~ /.*snapshot.*/)][*].parameters[?(@.in == 'path')].name
error
bright-data-no-trailing-slash
Bright Data paths must not include trailing slashes.
$.paths
warn
bright-data-error-response
Mutating operations should document a 4xx response.
$.paths[*][post,put,delete,patch].responses