Enable Banking · API Governance Rules
Enable Banking API Rules
Spectral linting rules defining API design standards and conventions for Enable Banking.
10 Rules
error 3
warn 6
Rule Categories
enable
Rules
error
enable-banking-info-title-required
Info object must have a title.
$.info
error
enable-banking-info-version-required
Info object must have a version.
$.info
warn
enable-banking-servers-must-include-production
Enable Banking specs should advertise https://api.enablebanking.com as the primary server.
$.servers
error
enable-banking-bearer-security-required
Enable Banking uses bearer JWT security; all operations should inherit bearerAuth.
$
warn
enable-banking-operation-id-snake-case
Operation IDs in Enable Banking specs follow snake_case_with_path suffix.
$.paths[*][get,post,put,patch,delete].operationId
warn
enable-banking-operation-summary-required
Every operation must have a summary.
$.paths[*][get,post,put,patch,delete]
hint
enable-banking-operation-summary-title-case
Operation summaries should be in Title Case.
$.paths[*][get,post,put,patch,delete].summary
warn
enable-banking-tag-allowed
Operations should be tagged with one of the four canonical Enable Banking tags.
$.paths[*][get,post,put,patch,delete].tags[*]
warn
enable-banking-no-trailing-slash
Enable Banking paths do not use trailing slashes.
$.paths
warn
enable-banking-no-internal-fields
Component schemas must not expose internal fields prefixed with underscore.
$.components.schemas[*].properties.*~