Reuters · API Governance Rules
Reuters API Rules
Spectral linting rules defining API design standards and conventions for Reuters.
8 Rules
error 2
warn 4
info 2
Rule Categories
reuters
Rules
warn
reuters-operation-id-camel-case
Operation IDs should use camelCase following Reuters Connect API convention.
$.paths[*][*].operationId
warn
reuters-summary-title-case
All operation summaries must use Title Case.
$.paths[*][*].summary
error
reuters-tags-defined
All operations must have at least one tag.
$.paths[*][*]
warn
reuters-token-auth
The Reuters Connect API uses token-based authentication via query parameter. All content endpoints must reference the tokenAuth security scheme.
$.paths[?(@property != '/login')][*]
info
reuters-xml-response-content
Reuters Connect API responses use XML content type.
$.paths[*][*].responses[*].content
warn
reuters-error-responses
All operations should define 401 and 403 error responses.
$.paths[*][*].responses
info
reuters-channel-param-required
Item list endpoints require a channel parameter.
$.paths['/items'].get.parameters
error
reuters-search-query-param
Search endpoint requires a query (q) parameter.
$.paths['/search'].get.parameters