Wikidata · API Governance Rules
Wikidata API Rules
Spectral linting rules defining API design standards and conventions for Wikidata.
33 Rules
error 12
warn 16
info 5
Rule Categories
delete
examples
get
info
no
openapi
operation
parameter
paths
request
response
schema
security
servers
tags
Rules
error
info-title-required
API info must have a title
$.info
warn
info-description-required
API info must have a description with sufficient detail
$.info
error
info-version-required
API info must have a version
$.info
warn
info-contact-required
API info should have contact information
$.info
warn
info-license-required
Open data APIs must declare their license (CC0 for Wikidata)
$.info
error
openapi-version-3
All Wikidata specs must use OpenAPI 3.x
$
error
servers-defined
Servers array must be defined
$
error
servers-https
Server URLs must use HTTPS
$.servers[*].url
warn
servers-description
Each server must have a description
$.servers[*]
warn
paths-kebab-case
Path segments must use kebab-case
$.paths[*]~
warn
paths-no-trailing-slash
Paths must not end with a trailing slash
$.paths[*]~
error
operation-summary-required
All operations must have a summary
$.paths[*][get,post,put,patch,delete,head,options]
warn
operation-description-required
All operations should have a description
$.paths[*][get,post,put,patch,delete,head,options]
error
operation-operation-id-required
All operations must have an operationId
$.paths[*][get,post,put,patch,delete,head,options]
warn
operation-operation-id-camel-case
operationId must use camelCase
$.paths[*][get,post,put,patch,delete,head,options].operationId
warn
operation-tags-required
All operations must have at least one tag
$.paths[*][get,post,put,patch,delete,head,options]
info
operation-summary-wikidata-prefix
Operation summaries should start with provider name "Wikidata"
$.paths[*][get,post,put,patch,delete,head,options].summary
warn
tags-global-defined
Global tags array must be defined
$
warn
tags-description-required
Global tags must have descriptions
$.tags[*]
warn
parameter-description-required
All parameters must have a description
$.paths[*][get,post,put,patch,delete].parameters[*]
error
parameter-schema-required
All parameters must define a schema
$.paths[*][get,post,put,patch,delete].parameters[*]
error
request-body-content-required
Request bodies must define content
$.paths[*][post,put,patch].requestBody
error
response-success-required
Every operation must define at least one 2xx response
$.paths[*][get,post,put,patch,delete]
error
response-description-required
All responses must have a description
$.paths[*][get,post,put,patch,delete].responses[*]
warn
response-401-for-authenticated
Authenticated operations should define a 401 response
$.paths[*][post,put,patch,delete]
info
schema-description-required
Top-level component schemas should have a description
$.components.schemas[*]
warn
schema-properties-types
Schema properties should define a type
$.components.schemas[*].properties[*]
warn
security-schemes-defined
Security schemes must be defined in components
$.components
info
security-scheme-description
Security schemes should have descriptions
$.components.securitySchemes[*]
error
get-no-request-body
GET operations must not have a request body
$.paths[*].get
info
delete-no-required-body
DELETE operations should return 200 or 204
$.paths[*].delete
warn
no-empty-descriptions
Descriptions must not be empty strings
$..description
info
examples-encouraged
Schema properties should have example values
$.components.schemas[*].properties[*]