Shodan · API Governance Rules
Shodan API Rules
Spectral linting rules defining API design standards and conventions for Shodan.
11 Rules
error 6
warn 5
Rule Categories
shodan
Rules
error
shodan-info-contact
Shodan APIs must declare a contact with email and URL.
$.info.contact
error
shodan-info-license
Shodan APIs must declare a license referencing the Shodan ToS.
$.info.license
error
shodan-server-https
All Shodan servers must be HTTPS endpoints under shodan.io.
$.servers[*].url
warn
shodan-security-apikey
All authenticated Shodan APIs must use the `apiKey` query-parameter scheme named `key`.
$.components.securitySchemes[?(@.type=='apiKey')]
error
shodan-operation-tags
Every operation must declare at least one tag.
$.paths[*][get,post,put,delete,patch]
error
shodan-operation-operationId
Every operation must have a camelCase operationId.
$.paths[*][get,post,put,delete,patch]
warn
shodan-operation-summary-title-case
Operation summaries should use Title Case.
$.paths[*][get,post,put,delete,patch].summary
warn
shodan-operation-description
Operations should have a description.
$.paths[*][get,post,put,delete,patch]
error
shodan-response-200
GET operations must define a 200 response.
$.paths[*].get
warn
shodan-parameter-description
Path and query parameters should be described.
$.paths[*][get,post,put,delete,patch].parameters[*]
warn
shodan-tag-defined
Tags used on operations must be defined at the document level.
$