Track-POD · API Governance Rules
Track-POD API Rules
Spectral linting rules defining API design standards and conventions for Track-POD.
7 Rules
error 3
warn 3
info 1
Rule Categories
track
Rules
error
track-pod-api-key-required
All operations must require the X-API-KEY API key security scheme.
$.paths[*][?(@property === 'get' || @property === 'post' || @property === 'put' || @property === 'delete' || @property === 'patch')]
warn
track-pod-pascalcase-paths
Track-POD paths use PascalCase resource segments (e.g. /Order, /VehicleCheck, /Route/Code/{code}).
$.paths
error
track-pod-operation-summary
Every operation must have a non-empty summary; Track-POD summaries use Title Case.
$.paths[*][get,post,put,delete,patch]
warn
track-pod-summary-title-case
Operation summaries should start with a capitalised verb (Get, Add, Update, Delete, Set, Complete, Reject).
$.paths[*][get,post,put,delete,patch].summary
error
track-pod-tag-each-operation
Every operation must declare at least one tag (Address, Driver, Order, RejectReason, Route, Test, Vehicle, VehicleCheck).
$.paths[*][get,post,put,delete,patch]
warn
track-pod-error-response
Mutating operations must document at least one non-2xx response.
$.paths[*][post,put,delete,patch].responses
info
track-pod-no-deprecated-status
Avoid the deprecated /Order/*/Status PUT endpoints; prefer /Order/*/Complete or /Order/*/Reject.
$.paths[?(@property =~ /\/Order\/(Number|Id|TrackId)\/[^/]+\/Status$/)]