UiPath · API Governance Rules
UiPath API Rules
Spectral linting rules defining API design standards and conventions for UiPath.
40 Rules
error 15
warn 20
info 5
Rule Categories
delete
external
get
info
no
openapi
operation
parameter
paths
request
response
schema
security
servers
tags
Rules
error
info-title-required
API title must be present and start with "UiPath"
$.info.title
error
info-description-required
API info must have a description with at least 50 characters
$.info.description
error
info-version-required
API info must include a version
$.info.version
warn
info-contact-url
API contact should include a URL
$.info.contact.url
warn
info-terms-of-service
API should reference UiPath terms of service
$.info.termsOfService
error
openapi-version
OpenAPI version must be 3.0.x or 3.1.x
$.openapi
error
servers-defined
At least one server must be defined
$.servers
error
servers-https
All server URLs must use HTTPS
$.servers[*].url
warn
servers-description
Each server should have a description
$.servers[*].description
warn
paths-kebab-case
Path segments must use kebab-case (no underscores or camelCase)
$.paths[*]~
warn
paths-no-trailing-slash
Paths must not have a trailing slash
$.paths[*]~
error
paths-no-query-string
Paths must not contain query strings
$.paths[*]~
error
operation-operationId-required
Every operation must have an operationId
$.paths[*][get,post,put,patch,delete,head,options]
warn
operation-operationId-camelCase
OperationId must use camelCase
$.paths[*][get,post,put,patch,delete].operationId
error
operation-summary-required
Every operation must have a summary
$.paths[*][get,post,put,patch,delete,head,options]
warn
operation-summary-uipath-prefix
Operation summary must start with "UiPath"
$.paths[*][get,post,put,patch,delete].summary
warn
operation-description-required
Every operation must have a description
$.paths[*][get,post,put,patch,delete,head,options]
error
operation-tags-required
Every operation must have at least one tag
$.paths[*][get,post,put,patch,delete]
info
operation-operationId-verb-prefix
OperationId should start with a standard verb (list, get, create, update, delete, add, remove, search, run, upload)
$.paths[*][get,post,put,patch,delete].operationId
warn
tags-global-defined
Global tags array should be defined
$.tags
warn
tags-description
All tags should have descriptions
$.tags[*].description
warn
parameter-description-required
Every parameter must have a description
$.paths[*][get,post,put,patch,delete].parameters[*]
warn
parameter-schema-type
Every parameter schema must have a type defined
$.paths[*][get,post,put,patch,delete].parameters[*].schema
info
parameter-pagination-pageSize
Pagination size parameter should be named 'pageSize' (not 'limit' or 'size')
$.paths[*][get].parameters[*]
error
parameter-no-api-key-in-query
API keys should be passed in headers, not query parameters
$.paths[*][get,post,put,patch,delete].parameters[?(@.name == 'api_key' || @.name == 'apiKey' || @.name == 'access_token')]
warn
request-body-json-content
Request body should include application/json content type
$.paths[*][post,put,patch].requestBody.content
info
request-body-description
Request body should have a description
$.paths[*][post,put,patch].requestBody
error
response-success-required
Every operation must define at least one 2xx response
$.paths[*][get,post,put,patch,delete].responses
warn
response-error-401
Operations should define a 401 Unauthorized response
$.paths[*][get,post,put,patch,delete].responses
warn
response-error-400
Operations with request bodies should define a 400 Bad Request response
$.paths[*][post,put,patch].responses
error
response-description-required
Every response must have a description
$.paths[*][get,post,put,patch,delete].responses[*]
warn
schema-description
Top-level schemas should have a description
$.components.schemas[*]
warn
schema-type-defined
Schema properties should have a type defined
$.components.schemas[*].properties[*]
info
schema-property-camelCase
Schema property names should use camelCase
$.components.schemas[*].properties[*]~
warn
security-schemes-defined
Security schemes should be defined in components
$.components.securitySchemes
warn
security-global-defined
Global security should be defined at the spec level
$.security
warn
delete-no-request-body
DELETE operations should not have a request body
$.paths[*].delete
error
get-no-request-body
GET operations must not have a request body
$.paths[*].get
error
no-empty-descriptions
Descriptions must not be empty strings
$..description
info
external-docs-encouraged
API spec should include externalDocs pointing to documentation
$.externalDocs