Dead Drop · API Governance Rules
Dead Drop API Rules
Spectral linting rules defining API design standards and conventions for Dead Drop.
8 Rules
error 3
warn 4
info 1
Rule Categories
dead
Rules
error
dead-drop-operation-summary-required
Every operation must have a non-empty summary.
$.paths[*][get,put,post,delete,patch,options,head]
warn
dead-drop-operation-summary-title-case
Operation summaries should use Title Case.
$.paths[*][get,put,post,delete,patch].summary
error
dead-drop-operation-tags-required
Every operation must have at least one tag.
$.paths[*][get,put,post,delete,patch]
warn
dead-drop-id-hex-pattern
Drop id schemas must enforce 64 lowercase hex characters.
$.paths['/drops/{id}'].parameters[?(@.name=='id')].schema
error
dead-drop-success-response-required
Each operation must declare a successful (2xx) response.
$.paths[*][get,put,post,delete,patch].responses
warn
dead-drop-terms-required-on-mutations
POST/PUT/DELETE drop endpoints must require I_agree_with_terms_and_conditions.
$.paths['/drops'].post.requestBody.content.application/json.schema.required
warn
dead-drop-error-envelope
Error responses must use the {error:{code,message}} envelope.
$.paths[*][get,put,post,delete,patch].responses[?(@property.match(/^[45]/))].content.application/json.schema.properties
info
dead-drop-encryption-algo-enum
encryptionAlgo enum should include pbkdf2-aes256-gcm-v1.
$..encryptionAlgo.enum