Robocorp · API Governance Rules
Robocorp API Rules
Spectral linting rules defining API design standards and conventions for Robocorp.
13 Rules
error 2
warn 7
info 4
Rule Categories
robocorp
Rules
warn
robocorp-operation-has-tag
All operations must have at least one tag
$.paths[*][get,post,put,patch,delete]
error
robocorp-operation-has-summary
All operations must have a summary
$.paths[*][get,post,put,patch,delete]
warn
robocorp-operation-has-description
All operations should have a description
$.paths[*][get,post,put,patch,delete]
error
robocorp-operation-has-operation-id
All operations must have an operationId
$.paths[*][get,post,put,patch,delete]
warn
robocorp-workspace-id-in-path
All resource paths should include workspace_id
$.paths[*]~
warn
robocorp-rc-wskey-auth
Control Room API uses RC-WSKEY prefixed API keys
$.components.securitySchemes[*]
warn
robocorp-delete-returns-204
DELETE operations should return 204 No Content
$.paths[*].delete
info
robocorp-post-create-returns-201
POST operations that create resources should return 201
$.paths[*].post
info
robocorp-list-operations-paginated
List operations should support pagination with cursor
$.paths[*].get
warn
robocorp-camel-case-operation-id
OperationIds should use camelCase
$.paths[*][get,post,put,patch,delete].operationId
info
robocorp-state-enum-defined
State fields should use defined enumerations
$.components.schemas[*].properties.state
info
robocorp-schema-has-description
Schema components should have descriptions
$.components.schemas[*]
warn
robocorp-has-error-response
Operations should define 401 unauthorized response
$.paths[*][get,post,put,patch,delete]