Home
Booking Holdings
Booking Holdings — booking com demand api rules
Booking Holdings — booking com demand api rules
Spectral linting rules defining API design standards and conventions for Booking Holdings.
30 Rules
error 10
warn 13
info 7
Generated by API Evangelist
Written by API Evangelist tooling for Booking Holdings's APIs. It is a starting point, not a ruleset Booking Holdings publishes or enforces.
Rule Categories
deprecation
global
info
no
openapi
operation
parameter
path
request
response
schema
security
server
servers
tag
Rules
error
info-title-required
API must declare an info.title.
$.info
warn
info-title-booking-prefix
Title should identify Booking.com.
$.info.title
warn
info-description-required
API must have a description (summary acceptable for 3.1).
$.info
error
info-version-required
API must declare a version.
$.info
warn
openapi-version-3-1
Booking.com Demand API specs are OpenAPI 3.1.0.
$.openapi
error
servers-defined
At least one server must be defined.
$.servers
error
server-https-only
All server URLs must use HTTPS.
$.servers[*].url
warn
server-description-required
Each server should describe its environment (e.g. Production, Sandbox).
$.servers[*]
warn
path-kebab-case
Path segments must be lowercase kebab-case.
$.paths[*]~
error
path-no-trailing-slash
Paths must not end with a trailing slash.
$.paths[*]~
error
path-no-query-string
Paths must not contain query strings.
$.paths[*]~
info
operation-post-only
Demand API endpoints are RPC-style POST operations; avoid GET/PUT/PATCH/DELETE.
$.paths[*]
warn
operation-summary-required
Every operation must have a summary.
$.paths[*][get,post,put,patch,delete]
warn
operation-summary-booking-prefix
Operation summaries should be prefixed with "Booking.com ".
$.paths[*][get,post,put,patch,delete].summary
error
operation-operationid-required
Every operation must have an operationId.
$.paths[*][get,post,put,patch,delete]
warn
operation-operationid-camelcase
operationId must be camelCase.
$.paths[*][get,post,put,patch,delete].operationId
warn
operation-tags-required
Every operation must declare at least one tag.
$.paths[*][get,post,put,patch,delete]
info
operation-microcks-extension
Operations should carry an x-microcks-operation extension for mock compatibility.
$.paths[*][get,post,put,patch,delete]
info
tag-title-case
Tag names should be Title Case (allowing a Common/Subgroup form).
$.paths[*][get,post,put,patch,delete].tags[*]
warn
parameter-description-required
Parameters must have a description.
$.paths[*][get,post,put,patch,delete].parameters[*]
info
parameter-snake-case
Parameter names should be snake_case.
$.paths[*][get,post,put,patch,delete].parameters[*].name
warn
request-body-json
Request bodies should accept application/json.
$.paths[*][post,put,patch].requestBody.content
error
response-2xx-required
Every operation must define a successful (2xx) response.
$.paths[*][get,post,put,patch,delete].responses
info
response-json-content
200 responses should return application/json.
$.paths[*][get,post,put,patch,delete].responses.200.content
info
schema-property-snake-case
Schema property names should be snake_case (Demand API convention).
$..properties.*~
error
global-security-defined
The API must declare global security.
$
error
security-scheme-bearer
A BearerAuth (HTTP bearer) security scheme must be defined.
$.components.securitySchemes
warn
security-scheme-is-bearer
BearerAuth must be an http bearer scheme.
$.components.securitySchemes.BearerAuth
warn
no-empty-descriptions
Descriptions, when present, must not be empty.
$..description
info
deprecation-documented
Deprecated operations should explain the deprecation in their description.
$.paths[*][get,post,put,patch,delete][?(@.deprecated == true)]
Spectral Ruleset
# authorship: generated by API Evangelist tooling. Stamped 2026-08-18
# on the file's own generator header (roadmap#64). An unmarked file is
# NOT assumed to be ours -- absence of evidence was never stamped.
x-method: generated
# Spectral ruleset for the Booking.com Demand API (Booking Holdings)
# Generated by the API Evangelist generate-spectral-rules skill.
# Enforces the conventions observed in openapi/booking-com-demand-api.yaml:
# - OpenAPI 3.1.0, POST-only RPC-style endpoints
# - kebab-case path segments under a /3.1 version host
# - snake_case schema/property and parameter naming
# - Bearer (Affiliate ID + token) authentication
# - Title Case tags, "Booking.com " summary prefix
extends: []
rules:
# ── INFO / METADATA ──────────────────────────────────────────────
info-title-required:
description: API must declare an info.title.
severity: error
given: $.info
then:
field: title
function: truthy
info-title-booking-prefix:
description: Title should identify Booking.com.
severity: warn
given: $.info.title
then:
function: pattern
functionOptions:
match: "Booking.com"
info-description-required:
description: API must have a description (summary acceptable for 3.1).
severity: warn
given: $.info
then:
field: summary
function: truthy
info-version-required:
description: API must declare a version.
severity: error
given: $.info
then:
field: version
function: truthy
# ── OPENAPI VERSION ──────────────────────────────────────────────
openapi-version-3-1:
description: Booking.com Demand API specs are OpenAPI 3.1.0.
severity: warn
given: $.openapi
then:
function: pattern
functionOptions:
match: "^3\\.1\\."
# ── SERVERS ──────────────────────────────────────────────────────
servers-defined:
description: At least one server must be defined.
severity: error
given: $.servers
then:
function: length
functionOptions:
min: 1
server-https-only:
description: All server URLs must use HTTPS.
severity: error
given: $.servers[*].url
then:
function: pattern
functionOptions:
match: "^https://"
server-description-required:
description: Each server should describe its environment (e.g. Production, Sandbox).
severity: warn
given: $.servers[*]
then:
field: description
function: truthy
# ── PATHS — NAMING CONVENTIONS ───────────────────────────────────
path-kebab-case:
description: Path segments must be lowercase kebab-case.
severity: warn
given: $.paths[*]~
then:
function: pattern
functionOptions:
match: "^(/([a-z0-9]+(-[a-z0-9]+)*|\\{[a-zA-Z0-9_]+\\}))+$"
path-no-trailing-slash:
description: Paths must not end with a trailing slash.
severity: error
given: $.paths[*]~
then:
function: pattern
functionOptions:
notMatch: ".+/$"
path-no-query-string:
description: Paths must not contain query strings.
severity: error
given: $.paths[*]~
then:
function: pattern
functionOptions:
notMatch: "\\?"
# ── OPERATIONS ───────────────────────────────────────────────────
operation-post-only:
description: Demand API endpoints are RPC-style POST operations; avoid GET/PUT/PATCH/DELETE.
severity: info
given: $.paths[*]
then:
field: post
function: truthy
operation-summary-required:
description: Every operation must have a summary.
severity: warn
given: $.paths[*][get,post,put,patch,delete]
then:
field: summary
function: truthy
operation-summary-booking-prefix:
description: Operation summaries should be prefixed with "Booking.com ".
severity: warn
given: $.paths[*][get,post,put,patch,delete].summary
then:
function: pattern
functionOptions:
match: "^Booking\\.com "
operation-operationid-required:
description: Every operation must have an operationId.
severity: error
given: $.paths[*][get,post,put,patch,delete]
then:
field: operationId
function: truthy
operation-operationid-camelcase:
description: operationId must be camelCase.
severity: warn
given: $.paths[*][get,post,put,patch,delete].operationId
then:
function: pattern
functionOptions:
match: "^[a-z][a-zA-Z0-9]*$"
operation-tags-required:
description: Every operation must declare at least one tag.
severity: warn
given: $.paths[*][get,post,put,patch,delete]
then:
field: tags
function: length
functionOptions:
min: 1
operation-microcks-extension:
description: Operations should carry an x-microcks-operation extension for mock compatibility.
severity: info
given: $.paths[*][get,post,put,patch,delete]
then:
field: x-microcks-operation
function: truthy
# ── TAGS ─────────────────────────────────────────────────────────
tag-title-case:
description: Tag names should be Title Case (allowing a Common/Subgroup form).
severity: info
given: $.paths[*][get,post,put,patch,delete].tags[*]
then:
function: pattern
functionOptions:
match: "^[A-Z][A-Za-z]+(/[a-z]+)?$"
# ── PARAMETERS ───────────────────────────────────────────────────
parameter-description-required:
description: Parameters must have a description.
severity: warn
given: $.paths[*][get,post,put,patch,delete].parameters[*]
then:
field: description
function: truthy
parameter-snake-case:
description: Parameter names should be snake_case.
severity: info
given: $.paths[*][get,post,put,patch,delete].parameters[*].name
then:
function: pattern
functionOptions:
match: "^[a-z][a-z0-9_]*$"
# ── REQUEST BODIES ───────────────────────────────────────────────
request-body-json:
description: Request bodies should accept application/json.
severity: warn
given: $.paths[*][post,put,patch].requestBody.content
then:
field: application/json
function: truthy
# ── RESPONSES ────────────────────────────────────────────────────
response-2xx-required:
description: Every operation must define a successful (2xx) response.
severity: error
given: $.paths[*][get,post,put,patch,delete].responses
then:
function: schema
functionOptions:
schema:
type: object
patternProperties:
"^2[0-9][0-9]$": true
minProperties: 1
response-json-content:
description: 200 responses should return application/json.
severity: info
given: $.paths[*][get,post,put,patch,delete].responses.200.content
then:
field: application/json
function: truthy
# ── SCHEMAS — PROPERTY NAMING ────────────────────────────────────
schema-property-snake-case:
description: Schema property names should be snake_case (Demand API convention).
severity: info
given: $..properties.*~
then:
function: pattern
functionOptions:
match: "^[a-z][a-z0-9_]*$"
# ── SECURITY ─────────────────────────────────────────────────────
global-security-defined:
description: The API must declare global security.
severity: error
given: $
then:
field: security
function: truthy
security-scheme-bearer:
description: A BearerAuth (HTTP bearer) security scheme must be defined.
severity: error
given: $.components.securitySchemes
then:
field: BearerAuth
function: truthy
security-scheme-is-bearer:
description: BearerAuth must be an http bearer scheme.
severity: warn
given: $.components.securitySchemes.BearerAuth
then:
- field: type
function: pattern
functionOptions:
match: "^http$"
- field: scheme
function: pattern
functionOptions:
match: "^bearer$"
# ── GENERAL QUALITY ──────────────────────────────────────────────
no-empty-descriptions:
description: Descriptions, when present, must not be empty.
severity: warn
given: $..description
then:
function: truthy
deprecation-documented:
description: Deprecated operations should explain the deprecation in their description.
severity: info
given: $.paths[*][get,post,put,patch,delete][?(@.deprecated == true)]
then:
field: description
function: truthy
Every ruleset here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for spectral rules
4 MCP tools reach this
find_rulesBrowse and filter every ruleset in the catalog.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.
All 92 tools →
Call it yourself
curl for this page
This ruleset
curl "https://apis.io/api/v1/rules/booking-com-demand-api-spectral-rules"
All spectral rules
curl "https://apis.io/api/v1/rules?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we
store it to create your key and to recognise you if you sign in with another
provider. See our Privacy Policy and
Terms .
A second provider on the same verified email joins the account you already have.