generated: '2026-09-17'
method: searched
source: https://developers.booking.com/connectivity/docs/deprecation-policy/deprecation-and-sunsetting
docs:
- https://developers.booking.com/connectivity/docs/deprecation-policy/deprecation-and-sunsetting
- https://developers.booking.com/connectivity/docs/migration-guides/migrating-to-new-versions
- https://developers.booking.com/demand/docs/additional-services/status-api/about
name: Booking.com API lifecycle
summary: >-
  Booking.com publishes one of the more complete deprecation regimes in travel: named definitions, a
  dated public table covering 30 retirements back to 2021, a stated runtime signal for both the
  deprecated and the sunset state, and named migration guides. What it does NOT publish is an SLA, a
  public status page, or a fixed minimum notice period - the notice window is set per retirement and
  has ranged from two weeks to two years.
versioning:
  scheme: URL path segment, per product
  demand_api:
    current: '3.2'
    also_published: ['3.1', 3.2-Beta]
    detail: >-
      Each version is a separate published OpenAPI document. 3.1 remains available and documented; the
      3.2-Beta track carries attractions, transfers, smart search, messaging and car availability ahead
      of GA.
  connectivity:
    detail: >-
      Endpoints version individually rather than as a suite - OTA_HotelProductNotif 1.0/1.1/1.2, rooms
      1.2/1.3, OTA_HotelRatePlanNotif 1.0/2.0 - and older versions are retired on the published table.
deprecation_policy:
  published: true
  url: https://developers.booking.com/connectivity/docs/deprecation-policy/deprecation-and-sunsetting
  definitions:
    solution: Any API product, feature or service - often an entire endpoint, part of an endpoint, or a single attribute.
    deprecation: >-
      Booking.com no longer intends to improve, update or actively support the solution technically or
      commercially. It remains usable, and business-critical bugs may still be fixed.
    sunsetting: The solution is no longer available at all.
    deprecation_announcement: Communicated ahead of the deprecation date so partners can plan the migration.
  runtime_signals:
    deprecated:
      whole_endpoint: A warning is returned in the response HEADER from the deprecation date.
      partial_endpoint: A warning is returned in the `warnings` array (JSON) or `<warnings>` element (XML) of the response body.
    sunset:
      behaviour: Calling a sunset endpoint or element returns HTTP 400 Bad request.
  rfc8594:
    sunset_header: false
    deprecation_header: false
    note: >-
      Booking.com does return a header warning on deprecation, but it does not document the RFC 8594
      Sunset header or the RFC 8594-style Deprecation header by name, and neither appears in the 20
      published specs. The mechanism is equivalent in intent but not in form, so a generic RFC 8594
      client will not pick it up.
  minimum_notice: not published
  notice_observed_range: 14 days to 24 months, from the published table
scheduled_retirements:
- solution: Versions 1.0, 1.1, 1.2 of GET OTA_HotelProductNotif
  deprecated: '2026-06-15'
  sunset: '2026-09-01'
- solution: Version 1.0 of POST OTA_HotelProductNotif
  deprecated: '2026-05-15'
  sunset: '2026-09-01'
- solution: Legacy max payable child field (max_children_that_pay_children_rate)
  deprecated: '2026-06-29'
  sunset: '2026-07-07'
  declared_in: openapi/booking-com-rooms-api-openapi.yml
  note: >-
    The only retirement in the table that is also declared inside a published contract - the Rooms API
    field description carries both dates inline.
- solution: OTA_HotelDescriptiveContentNotif (HDCN) endpoint in Content API
  deprecated: '2024-12-31'
  sunset: '2026-12-31'
- solution: OTA_HotelSummaryNotif (HSN) endpoint in Content API
  deprecated: '2024-12-31'
  sunset: '2026-12-31'
- solution: OTA_HotelInvNotif (HIN) endpoint in Content API for Home providers
  deprecated: '2024-12-31'
  sunset: '2026-12-31'
- solution: OTA_HotelDescriptiveInfo (HDI) endpoint in Content API for Home providers
  deprecated: '2024-12-31'
  sunset: '2026-12-31'
- solution: House Rules in Content API
  deprecated: '2024-12-31'
  sunset: '2026-12-31'
completed_retirements:
- solution: Credential-based authentication scheme
  deprecated: '2025-06-30'
  sunset: '2025-12-31'
  note: Replaced by token-based (JWT) authentication. See authentication/booking-com-authentication.yml.
- solution: Version 1.0 of OTA_HotelRatePlanNotif
  deprecated: '2025-10-13'
  sunset: '2026-01-29'
- solution: Generation of authorization tokens for messaging
  deprecated: '2025-10-08'
  sunset: '2025-12-15'
- solution: currencies endpoint (B.XML)
  deprecated: '2025-06-22'
  sunset: '2025-09-22'
- solution: Reply Score in Property Score API
  deprecated: '2025-04-30'
  sunset: '2025-07-02'
- solution: Version 1.0 of /hotels/xml/derivedprices
  deprecated: '2025-02-14'
  sunset: '2025-05-05'
retirement_table_note: >-
  The published table carries 30 rows in total running back to September 2021 (SPO flow, photos via
  Content API, one-past-stay guest requirement). The rows above are the currently-relevant window;
  the full table is at the policy URL.
deprecated_in_contract:
- spec: openapi/booking-com-demand-api-3-2-openapi.yml
  item: cancellation_type_filter enum value non_refundable
  note: Marked "DEPRECATED ... will be removed in further versions" in the schema description, with no date.
- spec: openapi/booking-com-rooms-api-openapi.yml
  item: max_children_that_pay_children_rate
  deprecated: '2026-06-29'
  sunset: '2026-07-07'
- spec: openapi/booking-com-demand-api-3-1-openapi.yml
  item: error.code / error.name
  note: Superseded by errors[].id in v3; documented as deprecated from V2.
status_page:
  public_page: false
  api: true
  url: https://developers.booking.com/demand/docs/additional-services/status-api/about
  spec: openapi/booking-com-status-api-openapi.yml
  host: https://partnerships-status.booking.com
  detail: >-
    Booking.com publishes no human status page - status.booking.com does not resolve and
    developers.booking.com/status is a 404. Instead it ships a Status API: a machine-readable operational
    status of monitored Demand API endpoint groups, intended to drive automated responses such as
    adjusting retry behaviour or switching to a fallback. The host answers 401 anonymously, so the feed
    is partner-gated - an agent cannot check Booking.com's health without credentials.
sla:
  published: false
  detail: No public SLA, uptime commitment or credit schedule is published for either programme.
support:
  demand: Account Manager (named per partner account)
  connectivity: https://connectivity.booking.com/s/article/Contact-Us