Truto · API Governance Rules
Truto API Rules
Spectral linting rules defining API design standards and conventions for Truto.
10 Rules
error 1
warn 6
info 3
Rule Categories
truto
Rules
warn
truto-operation-ids-camel-case
Truto operation IDs must use camelCase format.
$.paths.*[get,post,put,patch,delete]
error
truto-bearer-auth-security
All Truto API endpoints must require Bearer token authentication.
$.paths.*[get,post,put,patch,delete]
info
truto-versioned-paths
Truto API paths should not require version prefixes (versioning handled by server URL).
$.paths
warn
truto-operations-tagged
All Truto API operations must have tags for grouping.
$.paths.*[get,post,put,patch,delete]
warn
truto-response-200-json
GET operations must include a 200 response with JSON content.
$.paths.*[get].responses.200
info
truto-post-201-response
POST creation operations should return 201 status.
$.paths.*[post]
warn
truto-id-string-type
Identifier fields (id, remoteId) must be string type.
$.components.schemas.*.properties[id,remoteId,candidateId,accountId,contactId,opportunityId,employeeId,applicationId,integratedAccountId]
warn
truto-date-time-format
Date/time fields must use date-time format.
$.components.schemas.*.properties[createdAt,updatedAt,appliedAt,openedAt,closedAt,completedAt,requestedAt]
info
truto-pagination-cursor
List endpoints should support cursor-based pagination.
$.paths.*[get]
warn
truto-integrated-account-param
Unified API list/get endpoints should include integrated_account_id parameter to specify the connected provider instance.
$.paths./unified/*/[get,post]