Transcend · API Governance Rules
Transcend API Rules
Spectral linting rules defining API design standards and conventions for Transcend.
10 Rules
error 4
warn 6
Rule Categories
transcend
Rules
error
transcend-info-contact
Every spec must declare a contact for the Transcend developer team.
$.info
warn
transcend-info-license
Top-level license information must be present.
$.info
error
transcend-operation-operationid
Every operation needs an operationId for SDK and MCP generation.
$.paths[*][get,post,put,delete,patch]
error
transcend-operation-tags-required
Every operation must have at least one tag.
$.paths[*][get,post,put,delete,patch]
warn
transcend-operation-summary-title-case
Operation summaries must use Title Case.
$.paths[*][get,post,put,delete,patch].summary
warn
transcend-v1-prefix
Versioned endpoints must live under /v1/ unless they are public keys, sync, llm, or classify utilities.
$.paths
error
transcend-security-defined
All operations should inherit the Transcend_API_Key scheme unless they are public-key endpoints.
$
warn
transcend-tag-required-domains
Tags should match the known Transcend domains (Data Subject Request, Preflight, Custom Integration, LLM Classifier, Public Keys, Preferences, Consent).
$.tags[*].name
warn
transcend-no-trailing-slash
Paths must not end with a trailing slash.
$.paths
warn
transcend-error-schema
Components should define a reusable Error schema.
$.components.schemas