Retool · API Governance Rules
Retool API Rules
Spectral linting rules defining API design standards and conventions for Retool.
9 Rules
error 3
warn 4
Rule Categories
retool
Rules
warn
retool-operation-id-camel-case
Operation IDs should use camelCase following the Retool API convention.
$.paths[*][*].operationId
warn
retool-operation-summary-title-case
All operation summaries must use Title Case.
$.paths[*][*].summary
error
retool-tags-defined
All operations must have at least one tag for grouping in the API reference.
$.paths[*][*]
warn
retool-response-200-schema
Successful GET responses must include a response schema.
$.paths[*].get.responses.200
error
retool-request-body-post-put
POST and PUT operations must include a request body.
$.paths[*][post,put]
warn
retool-error-responses
Operations should document 401 and 403 error responses.
$.paths[*][get,post,put,delete].responses
hint
retool-uuid-path-params
User ID path parameters should be named 'userId' and use UUID format.
$.paths[*][*].parameters[?(@.in == 'path' && @.name == 'id')]
error
retool-bearer-auth-scheme
The Retool API uses Bearer token authentication exclusively.
$.components.securitySchemes[*]
hint
retool-pagination-parameters
List endpoints returning collections should support page and pageSize parameters.
$.paths[*].get