Vonage · API Governance Rules
Vonage API Rules
Spectral linting rules defining API design standards and conventions for Vonage.
11 Rules
error 1
warn 4
info 6
Rule Categories
vonage
Rules
warn
vonage-operation-ids-camel-case
Operation IDs must use camelCase.
$.paths[*][*].operationId
warn
vonage-tags-title-case
Tags must use Title Case.
$.paths[*][*].tags[*]
error
vonage-operation-summary-required
All operations must have a summary.
$.paths[*][get,post,put,patch,delete]
warn
vonage-operation-tags-required
All operations must have at least one tag.
$.paths[*][get,post,put,patch,delete]
warn
vonage-response-200-defined
GET operations must define a 200 response.
$.paths[*].get
info
vonage-response-201-post
POST create operations should return 201.
$.paths[*].post
info
vonage-api-key-secret-in-body
Vonage REST API (rest.nexmo.com) uses api_key and api_secret in request body. Ensure these are documented as required fields.
$.paths[/sms/json,/account/numbers,/number/search,/number/buy,/number/cancel,/number/update][post,get].requestBody.content[*].schema.required
info
vonage-bearer-auth-voice
Voice API operations must use Bearer JWT authentication.
$.paths[/v1/calls,/v1/calls/*][*].security[*]
info
vonage-description-required
All operations should have a description.
$.paths[*][get,post,put,patch,delete]
info
vonage-path-kebab-case
API paths should use kebab-case segments.
$.paths
info
vonage-parameters-described
All parameters should have descriptions.
$.paths[*][*].parameters[*]