wells-fargo · API Governance Rules
wells-fargo API Rules
Spectral linting rules defining API design standards and conventions for wells-fargo.
12 Rules
error 4
warn 7
Rule Categories
api
oauth2
operation
pagination
path
query
response
Rules
warn
api-versioned-paths
All Wells Fargo API paths must include a version segment (/v1/, /v2/, /v3/).
$.paths[*]~
error
oauth2-security-scheme
APIs must use OAuth 2.0 security scheme.
$.components.securitySchemes[*]
error
operation-security-scopes
All operations must declare security requirements with scopes.
$.paths[*][get,post,put,patch,delete]
error
operation-id-required
All operations must have an operationId.
$.paths[*][get,post,put,patch,delete]
warn
operation-id-camel-case
Operation IDs must use lowerCamelCase naming.
$.paths[*][*].operationId
warn
path-params-camel-case
Path parameter names should use lowerCamelCase.
$.paths[*][*].parameters[?(@.in=='path')].name
warn
query-params-camel-case
Query parameter names should use lowerCamelCase.
$.paths[*][*].parameters[?(@.in=='query')].name
error
operation-summary-required
All operations must have a summary.
$.paths[*][get,post,put,patch,delete]
warn
operation-summary-title-case
Operation summaries must use Title Case.
$.paths[*][*].summary
warn
response-401-defined
Operations with security must define a 401 response.
$.paths[*][get,post,put,patch,delete].responses
warn
response-400-on-write
POST and PUT operations must define a 400 response for validation errors.
$.paths[*][post,put].responses
hint
pagination-page-size-param
Paginated GET endpoints should use pageSize and pageToken parameters.
$.paths[*].get.parameters[*].name