Docling · API Governance Rules
Docling API Rules
Spectral linting rules defining API design standards and conventions for Docling.
6 Rules
error 1
warn 5
Rule Categories
docling
Rules
warn
docling-operation-summary-title-case
Operation summaries should use Title Case.
$.paths.*[get,post,put,patch,delete,options].summary
warn
docling-versioned-paths
API paths exposed by Docling Serve must be versioned under `/v1/`.
$.paths
warn
docling-operation-id-camel-case
operationId should be camelCase.
$.paths.*[get,post,put,patch,delete].operationId
error
docling-task-id-path-param
Endpoints under /v1/status/poll/ and /v1/result/ must declare a task_id path parameter.
$.paths[?(@property == '/v1/status/poll/{task_id}' || @property == '/v1/result/{task_id}')].*.parameters[?(@.in == 'path')].name
warn
docling-tag-defined
Every operation must carry a tag.
$.paths.*[get,post,put,patch,delete].tags
warn
docling-json-content-type
Sync conversion endpoints should advertise application/json responses.
$.paths[?(@property == '/v1/convert/source' || @property == '/v1/convert/file')].post.responses.200.content