Riot Games · API Governance Rules
Riot Games API Rules
Spectral linting rules defining API design standards and conventions for Riot Games.
10 Rules
error 4
warn 5
info 1
Rule Categories
riot
Rules
warn
riot-operation-summary-title-case
All operation summaries must use Title Case
$.paths[*][get,post,put,patch,delete].summary
warn
riot-operation-id-camel-case
Operation IDs should be camelCase
$.paths[*][get,post,put,patch,delete].operationId
warn
riot-tags-title-case
Tags must use Title Case
$.paths[*][get,post,put,patch,delete].tags[*]
error
riot-must-have-api-key-security
All operations must require X-Riot-Token API key
$.paths[*][get,post,put,patch,delete]
error
riot-responses-must-include-200
GET operations must return a 200 response
$.paths[*].get
warn
riot-must-have-403-response
Operations must include 403 Forbidden response for API key errors
$.paths[*][get,post,put,patch,delete].responses
warn
riot-must-have-404-response
Operations must include 404 Not Found response for resource lookups
$.paths[*].get.responses
error
riot-path-parameters-required
Path parameters must be marked as required
$.paths[*][get,post,put,patch,delete].parameters[?(@.in == 'path')]
error
riot-servers-must-be-https
All servers must use HTTPS
$.servers[*].url
info
riot-encrypted-ids-in-descriptions
Operations using encrypted IDs should document encryption in description
$.paths[*][get,post,put,patch,delete].parameters[?(@.name =~ /encrypted/i)]