Paystack · API Governance Rules
Paystack API Rules
Spectral linting rules defining API design standards and conventions for Paystack.
10 Rules
error 2
warn 7
Rule Categories
paystack
Rules
warn
paystack-operation-summary-title-case
Operation summaries should use Title Case (matches Paystack API Reference style).
$.paths[*][get,post,put,delete,patch].summary
warn
paystack-operation-id-snake-case
operationId should be snake_case prefixed with the resource (e.g. transaction_initialize).
$.paths[*][get,post,put,delete,patch].operationId
warn
paystack-operation-description
Every operation must have a description.
$.paths[*][get,post,put,delete,patch]
error
paystack-operation-tag-required
Every operation must have at least one tag (used to group by product API).
$.paths[*][get,post,put,delete,patch]
warn
paystack-server-base-url
Paystack production servers should use api.paystack.co.
$.servers[*].url
error
paystack-security-bearer-required
A global security requirement using bearerAuth must be present.
$
warn
paystack-no-trailing-slash
Paths must not end with a trailing slash.
$.paths
warn
paystack-response-envelope-status-message-data
2xx JSON responses should expose the `status`, `message`, and `data` envelope used across the Paystack API.
$.paths[*][get,post,put,delete,patch].responses['200','201'].content['application/json'].schema.properties
warn
paystack-amount-integer
Monetary `amount` fields must be integers (lowest denomination — kobo/pesewas/cents).
$..properties.amount
hint
paystack-currency-enum
Currency fields should be constrained to Paystack-supported ISO 4217 codes.
$..properties.currency