Langflow · API Governance Rules
Langflow API Rules
Spectral linting rules defining API design standards and conventions for Langflow.
6 Rules
warn 3
info 1
Rule Categories
langflow
Rules
warn
langflow-api-prefix
Langflow REST paths must be served under /api/v1 or /api/v2 (health and logs are exempt).
$.paths.*~
warn
langflow-operation-summary
Every operation must have a Title Case summary.
$.paths[*][get,post,put,patch,delete]
warn
langflow-operation-tags
Every operation must carry at least one tag for grouping in the Langflow docs.
$.paths[*][get,post,put,patch,delete]
info
langflow-apikey-security
Components must declare the x-api-key API key security scheme used by Langflow.
$.components.securitySchemes
hint
langflow-no-trailing-slash-inconsistency
Avoid offering both `/foo` and `/foo/` for the same resource. Langflow's v2 Files API does this — flag it.
$.paths.*~
hint
langflow-flow-id-param-naming
Path parameters that identify a flow should be named `flow_id` or `flow_id_or_name`.
$.paths.*~