Frontegg · API Governance Rules
Frontegg API Rules
Spectral linting rules defining API design standards and conventions for Frontegg.
9 Rules
error 3
warn 3
info 3
Rule Categories
frontegg
Rules
error
frontegg-audits-operation-summary-required
Every operation MUST have a summary describing it.
$.paths[*][*]
warn
frontegg-audits-summary-title-case
Operation summaries MUST be in Title Case (Frontegg convention).
$.paths[*][*].summary
error
frontegg-audits-operation-tag-required
Every operation MUST have at least one tag.
$.paths[*][*]
warn
frontegg-audits-tag-title-case
Tag names MUST be in Title Case.
$.paths[*][*].tags[*]
warn
frontegg-audits-regional-server
Servers MUST include at least one regional Frontegg gateway (api.frontegg.com, api.us.frontegg.com, api.au.frontegg.com, api.ca.frontegg.com).
$.servers[*].url
info
frontegg-audits-bearer-auth-required
Frontegg APIs use JWT Bearer authentication; components.securitySchemes SHOULD declare it.
$
info
frontegg-audits-frontegg-tenant-header
When environment tokens are used, the frontegg-tenant-id header SHOULD be available as a parameter on management operations.
$.paths[*][*].parameters
error
frontegg-audits-response-2xx-required
Every operation MUST declare at least one 2xx response.
$.paths[*][*].responses
info
frontegg-audits-error-response-401
Authenticated operations SHOULD document 401 responses.
$.paths[*][*].responses