Teller · API Governance Rules
Teller API Rules
Spectral linting rules defining API design standards and conventions for Teller.
12 Rules
error 7
warn 5
Rule Categories
teller
Rules
warn
teller-operation-summary-title-case
All operation summaries must use Title Case
$.paths[*][*].summary
error
teller-operation-must-have-operationid
All operations must have an operationId
$.paths[*][*]
warn
teller-operationid-camelcase
Operation IDs should use camelCase
$.paths[*][*].operationId
error
teller-server-must-be-api-teller
Server URL must use api.teller.io
$.servers[*].url
warn
teller-account-id-path-parameter
Account ID path parameters should be named account_id
$.paths['/accounts/{account_id}'][*].parameters[?(@.in == 'path')]
error
teller-response-must-have-401
All authenticated operations must handle 401 Unauthorized
$.paths['/accounts'][get].responses
warn
teller-response-must-have-429
GET operations should handle 429 rate limiting
$.paths[*].get.responses
error
teller-delete-returns-204
DELETE operations must return 204 No Content
$.paths[*].delete.responses
warn
teller-amount-as-string
Financial amounts should be represented as string type to preserve precision
$.components.schemas[*].properties.amount
error
teller-transaction-status-enum
Transaction status must use approved enum values
$.components.schemas.Transaction.properties.status
error
teller-account-type-enum
Account type must use approved enum values
$.components.schemas.Account.properties.type
error
teller-bearer-mtls-security-scheme
Security scheme must use bearer type for mTLS access tokens
$.components.securitySchemes.BearerMtls