Tabby · API Governance Rules
Tabby API Rules
Spectral linting rules defining API design standards and conventions for Tabby.
10 Rules
error 7
warn 3
Rule Categories
tabby
Rules
error
tabby-info-title-present
Tabby OpenAPI specs MUST declare an info.title that begins with "Tabby".
$.info.title
error
tabby-server-host-allowlist
Tabby production hosts are api.tabby.ai (UAE/Kuwait) and api.tabby.sa (KSA) only.
$.servers[*].url
error
tabby-paths-versioned
All Tabby endpoints MUST be versioned (/api/v1 or /api/v2).
$.paths[*]~
warn
tabby-operation-id-camel-case
Tabby operationIds follow camelCase convention (e.g. postCheckoutSession).
$.paths[*][*].operationId
warn
tabby-operation-summary-title-case
Operation summaries MUST use Title Case.
$.paths[*][*].summary
error
tabby-bearer-auth-required
Tabby endpoints MUST be secured with bearer authentication (secret_key scope).
$.paths[*][*].security[*]
error
tabby-currency-enum
Tabby currency fields MUST be limited to AED, SAR, or KWD.
$.components.schemas..properties.currency.enum
error
tabby-language-enum
Tabby lang fields MUST be limited to ar or en.
$.components.schemas..properties.lang.enum
error
tabby-amount-string-type
Tabby monetary amounts are transferred as decimal-encoded strings, not numbers.
$.components.schemas..properties.amount.type
warn
tabby-reference-id-required-on-mutations
Capture, refund, and similar mutating operations MUST require a reference_id (idempotency).
$.paths[*][post].requestBody.content.[application/json].schema.required