Delft University of Technology · API Governance Rules
Delft University of Technology API Rules
Spectral linting rules defining API design standards and conventions for Delft University of Technology.
10 Rules
error 8
warn 2
Rule Categories
tu
Rules
error
tu-delft-info-contact
The description must name a reachable operator contact.
$.info
error
tu-delft-server-is-institutional
The only server may be data.4tu.nl — a vendor host here would be a misattribution.
$.servers[*].url
error
tu-delft-operation-id
Every operation carries an operationId.
$.paths[*][get,post,put,patch,delete]
error
tu-delft-operation-tagged
Every operation is tagged so the description can be split by resource.
$.paths[*][get,post,put,patch,delete]
warn
tu-delft-operation-summary
Every operation carries a summary.
$.paths[*][get,post,put,patch,delete]
error
tu-delft-404-documented
Every path that takes a uuid must document the 404 the service actually returns.
$.paths[?(@property.match(/\{uuid\}/))][get]
error
tu-delft-account-secured
Endpoints under /v2/account/ must declare tokenAuth.
$.paths[?(@property.match(/^\/v2\/account\//))][get,post,put,delete]
warn
tu-delft-uuid-format
The uuid path parameter must be typed as a uuid, not a bare string.
$.components.parameters.Uuid.schema
error
tu-delft-provenance-block
The description must carry the x-artifact provenance block; an unmarked artifact is credited to the institution.
$
error
tu-delft-operator-declared
The provenance block must declare who operates the thing described.
$.x-artifact