Tazama · API Governance Rules
Tazama API Rules
Spectral linting rules defining API design standards and conventions for Tazama.
10 Rules
error 2
warn 8
Rule Categories
tazama
Rules
warn
tazama-iso20022-paths
ISO 20022 transaction paths should follow the /v1/evaluate/iso20022/{messageType} pattern
$.paths[*]~
error
tazama-operation-ids-required
All operations must have operationId defined
$.paths[*][get,post,put,delete,patch]
warn
tazama-operation-ids-kebab-case
operationId values should use camelCase convention consistent with Tazama TypeScript codebase
$.paths[*][get,post,put,delete,patch].operationId
warn
tazama-request-body-json
POST endpoints accepting transaction data should require application/json content type
$.paths[*].post.requestBody.content
error
tazama-response-200-defined
All operations should define a 200 or 201 success response
$.paths[*][get,post,put,delete,patch].responses
warn
tazama-error-responses
All operations should define 400 and 500 error responses
$.paths[*][post].responses
warn
tazama-info-contact
API info should include contact information
$.info
warn
tazama-tags-defined
All operations should be tagged for proper grouping
$.paths[*][get,post,put,delete,patch]
warn
tazama-description-required
Operations should have descriptions explaining their purpose
$.paths[*][get,post,put,delete,patch]
warn
tazama-schemas-named
All schemas in components should be named using PascalCase
$.components.schemas[*]~