Kinde · API Governance Rules
Kinde API Rules
Spectral linting rules defining API design standards and conventions for Kinde.
12 Rules
error 2
warn 8
info 2
Rule Categories
kinde
Rules
warn
kinde-operation-summary-title-case
All operation summaries must use Title Case.
$.paths[*][*].summary
warn
kinde-operation-id-camel-case
OperationIds use camelCase across the Kinde API surface.
$.paths[*][*].operationId
error
kinde-tags-required
Every operation must declare at least one tag for grouping in the docs.
$.paths[*][*]
warn
kinde-tags-title-case
Top-level tags must be Title Case.
$.tags[*].name
error
kinde-bearer-auth-required
The Kinde Management API requires Bearer (M2M) authentication.
$.components.securitySchemes
warn
kinde-server-subdomain-template
Server URL must use the {subdomain}.kinde.com template.
$.servers[*].url
warn
kinde-version-in-path
All API paths should include the /api/v1 or /account_api/v1 version prefix.
$.paths
info
kinde-pagination-page-size-integer
List endpoints exposing page_size must declare it as an integer query parameter.
$.paths[*][get].parameters[?(@.name=='page_size')]
info
kinde-cursor-pagination-starting-after
List endpoints should use a starting_after cursor for pagination rather than offset.
$.paths[*][get].parameters[*].name
warn
kinde-snake-case-query-params
Kinde uses snake_case for query parameters.
$.paths[*][*].parameters[?(@.in=='query')].name
warn
kinde-snake-case-path-params
Kinde uses snake_case for path parameters too.
$.paths[*][*].parameters[?(@.in=='path')].name
warn
kinde-error-response-defined
Operations should define at least one 4xx error response.
$.paths[*][*].responses