PropelAuth · API Governance Rules
PropelAuth API Rules
Spectral linting rules defining API design standards and conventions for PropelAuth.
7 Rules
error 1
warn 6
Rule Categories
propelauth
Rules
error
propelauth-info-contact
Info object MUST include PropelAuth support contact.
$.info.contact
warn
propelauth-server-base-path
Server URL MUST point at a PropelAuth Auth URL (custom domain or *.propelauthtest.com).
$.servers[*].url
warn
propelauth-bearer-auth-required
All backend operations MUST require BackendApiKey (bearer) authentication.
$.security
warn
propelauth-operation-summary-title-case
Every operation summary MUST use Title Case.
$.paths[*][get,post,put,patch,delete].summary
warn
propelauth-operation-id-camel-case
operationId MUST be camelCase.
$.paths[*][get,post,put,patch,delete].operationId
warn
propelauth-tag-defined
Operations MUST reference at least one tag.
$.paths[*][get,post,put,patch,delete]
warn
propelauth-path-backend-prefix
Backend API operations MUST live under /api/backend/v1/ (the public PropelAuth backend prefix).
$.paths