RelativityOne · API Governance Rules
RelativityOne API Rules
Spectral linting rules defining API design standards and conventions for RelativityOne.
10 Rules
error 3
warn 5
info 2
Rule Categories
relativityone
Rules
warn
relativityone-workspace-scoped-path
All resource paths should include a workspaceId parameter to scope operations to a workspace.
$.paths[*]
warn
relativityone-integer-artifact-ids
Path parameters named workspaceId, projectId, taskId, entityId should be integer type.
$.paths[*][*].parameters[?(@.name =~ /Id$/ && @.in == 'path')].schema
error
relativityone-operation-tags
All operations should have at least one tag for grouping in documentation.
$.paths[*][*]
error
relativityone-operation-ids
All operations must have unique operationIds in camelCase.
$.paths[*][*]
warn
relativityone-operation-id-camel-case
OperationIds should use camelCase naming convention.
$.paths[*][*].operationId
warn
relativityone-title-case-summaries
Operation summaries should use Title Case.
$.paths[*][*].summary
warn
relativityone-response-descriptions
All response codes should have descriptions.
$.paths[*][*].responses[*]
error
relativityone-json-content-type
Request bodies should use application/json content type.
$.paths[*][post,put,patch].requestBody.content
info
relativityone-schema-descriptions
Schema properties should have descriptions for API clarity.
$.components.schemas[*].properties[*]
info
relativityone-pagination-on-lists
GET operations returning lists should support start and length pagination parameters.
$.paths[*].get