U.S. Bureau of Labor Statistics · API Governance Rules
U.S. Bureau of Labor Statistics API Rules
Spectral linting rules defining API design standards and conventions for U.S. Bureau of Labor Statistics.
33 Rules
error 9
warn 17
info 7
Rule Categories
bls
get
info
no
openapi
operation
parameter
paths
request
response
schema
security
servers
tags
Rules
error
info-title-required
API title must be present and include "BLS" or "Bureau of Labor Statistics".
$.info.title
warn
info-description-required
API info must have a description with at least 50 characters.
$.info
error
info-version-required
API version must be specified.
$.info
warn
info-contact-required
Contact information should be provided.
$.info
warn
openapi-version-3
All BLS API specs must use OpenAPI 3.0.x.
$
error
servers-defined
At least one server must be defined.
$
error
servers-https
All server URLs must use HTTPS.
$.servers[*].url
warn
servers-bls-domain
Server URL should point to api.bls.gov.
$.servers[*].url
warn
paths-kebab-case
Path segments must use kebab-case (lowercase letters, numbers, hyphens, or {params}).
$.paths[*]~
info
paths-no-trailing-slash
Paths should not have trailing slashes (except the multiple series POST endpoint).
$.paths[*]~
info
paths-versioned
All paths should be accessed via a versioned server URL (v1 or v2).
$.servers[*].url
error
operation-summary-required
All operations must have a summary.
$.paths[*][get,post,put,patch,delete]
warn
operation-summary-prefix
Operation summaries should start with "U.S. Bureau of Labor Statistics".
$.paths[*][get,post,put,patch,delete].summary
warn
operation-description-required
All operations must have a description.
$.paths[*][get,post,put,patch,delete]
error
operation-id-required
All operations must have an operationId.
$.paths[*][get,post,put,patch,delete]
warn
operation-id-camel-case
OperationIds should use camelCase.
$.paths[*][get,post,put,patch,delete].operationId
warn
operation-tags-required
All operations must have at least one tag.
$.paths[*][get,post,put,patch,delete]
info
tags-defined
Global tags array should be defined.
$
warn
parameter-description-required
All parameters must have a description.
$.paths[*][get,post,put,patch,delete].parameters[*]
error
parameter-schema-required
All parameters must have a schema.
$.paths[*][get,post,put,patch,delete].parameters[*]
info
parameter-snake-case
Query and path parameter names should use snake_case.
$.paths[*][get,post,put,patch,delete].parameters[?(@.in == 'query' || @.in == 'path')].name
warn
request-body-json
POST request bodies should use application/json content type.
$.paths[*].post.requestBody.content
error
response-success-required
All operations must define a 200 response.
$.paths[*][get,post,put,patch,delete].responses
warn
response-400-defined
Operations should define a 400 Bad Request response.
$.paths[*][get,post,put,patch,delete].responses
warn
response-description-required
All response definitions must have a description.
$.paths[*][get,post,put,patch,delete].responses[*]
warn
schema-description-required
All top-level component schemas should have a description.
$.components.schemas[*]
info
schema-property-snake-case
Schema property names should use snake_case.
$.components.schemas[*].properties[*]~
warn
security-scheme-defined
Security schemes should be defined in components.
$.components.securitySchemes
info
security-scheme-description
Security schemes should have a description.
$.components.securitySchemes[*]
error
get-no-request-body
GET operations must not have a request body.
$.paths[*].get
warn
no-empty-descriptions
Descriptions should not be empty strings.
$..description
info
bls-status-field-documented
BLS API responses include a 'status' field; schemas should document it.
$.components.schemas.SeriesResponse.properties
warn
bls-registration-key-optional
registrationkey parameter should not be marked as required (public endpoints work without it).
$.paths[*][get,post].parameters[?(@.name == 'registrationkey')].required