Resend · API Governance Rules
Resend API Rules
Spectral linting rules defining API design standards and conventions for Resend.
11 Rules
error 3
warn 6
info 2
Rule Categories
resend
Rules
error
resend-operation-id
All operations must have an operationId.
$.paths[*][get,post,put,patch,delete]
error
resend-operation-summary
All operations must have a summary in Title Case.
$.paths[*][get,post,put,patch,delete]
warn
resend-bearer-auth
All operations should use Bearer token authentication.
$.paths[*][*]
error
resend-response-200-or-201
All operations should have a 200 or 201 success response.
$.paths[*][get,post,put,patch,delete].responses
warn
resend-request-body-post
POST operations that create resources should have a request body.
$.paths[*].post
info
resend-path-resource-id
Path parameters for resource IDs should use snake_case with _id suffix.
$.paths[*].parameters[?(@.in == 'path')]
warn
resend-path-plural-nouns
Collection paths should use plural nouns.
$.paths[?([email protected](/{.*}/))][*]~
warn
resend-tags-title-case
All tags must use Title Case.
$.tags[*].name
warn
resend-operation-tags
All operations must have at least one tag.
$.paths[*][get,post,put,patch,delete]
warn
resend-response-schema
Success responses should reference a schema.
$.paths[*][*].responses[200,201].content.application/json.schema
info
resend-rate-limit-documented
API should document rate limiting behavior.
$.info