Reservation & Booking Management

BC-4020 Level 1 Travel & Hospitality 28 providers 71 API surfaces 2 rated strong or better

Lifecycle of the reservation, PNR, and hotel folio — capture, modification, cancellation, group blocks, confirmations, payments, and disruption-driven rebooking — independent of which channel originated the booking.

Reservation & Booking Management (BC-4020) is a level-1 business capability in the Travel & Hospitality model. The catalog holds 71 API surface(s) from 28 provider(s) that can perform some part of it, 2 of them rated strong or better. Reach is the vendor surface that lands on this capability — it is not a claim about what any particular organisation has deployed.

Where this capability definition comes from. This capability is part of a published business-architecture model that API Evangelist did not author. It is redistributed here under CC-BY-4.0. Turbo EA Capabilities by Vincent Verdet — Turbo EA, https://github.com/vincentmakes/turbo-ea-capabilities, CC BY 4.0 Changes: Consolidated from 333 per-L1 YAML files into one JSON; English only (upstream i18n/ omitted); descriptions whitespace-normalised. No capability was added, removed, renamed or re-parented. Source repository · NOTICE and third-party framework attributions

Authorities this capability cites

Cited by the capability model itself. These frameworks are referenced, never redistributed, and citing one does not imply its owner endorses this listing.

Sub-capabilities

Reservation Capture BC-4020.10

Capture of reservations across simple and complex travel itineraries from any originating channel or agent.

14 providers, 17 API surfaces

Booking Modification & Cancellation BC-4020.20

Voluntary modification and cancellation of bookings, including change fees, refund eligibility, and reissue operations.

8 providers, 11 API surfaces

Group Block Management BC-4020.30

Management of group blocks against contracted inventory — block creation, rooming lists, cut-off, and pickup tracking.

no catalog coverage

Reservation Confirmation & Documentation BC-4020.40

Issuance of booking confirmations, vouchers, e-tickets, and itinerary documents to travellers and agents.

1 provider, 1 API surface

Reservation Hold & Waitlist Management BC-4020.50

Management of provisional holds, waitlists, and conversions when live availability is constrained or terms require time-to-pay.

no catalog coverage

Booking Payment & Settlement BC-4020.60

Booking-level payment, deposit, charge capture, and partner settlement including BSP and ARC.

7 providers, 11 API surfaces

Booking Disruption & Rebooking Operations BC-4020.70

Reaccommodation of bookings affected by schedule changes, cancellations, and mass disruptions, including communications and compensation eligibility.

1 provider, 1 API surface

Providers that reach this capability

Ordered by rating band. Reach means a provider publishes an API surface that can perform some part of this capability — it is not a claim that any particular organisation has deployed it.

Exemplar 1 Complete, well-documented, and agent-ready
Strong 1 Solid coverage with minor gaps
Developing 9 Usable, with meaningful gaps to close
Thin 15 Limited public surface area
Emerging 1 Early or largely undocumented
Minimal 1 Almost no public developer surface

Workflows that realise this capability

Arazzo workflows whose own sourceDescriptions call APIs that carry this capability. The link is derived, not asserted: each workflow declares x-realizes-capability-ids with the spec and confidence behind it.

This page carries no rating. Capabilities are not rated. A capability is a description of what a business does, not a thing a company publishes, so a Kin Score would have nothing to measure.
The edge table is a Pro feature. This page shows which providers and tags reach Reservation & Booking Management. The underlying tag → capability edges — each with the quoted fragment of the provider's own OpenAPI that evidences it, a calibrated confidence score, and the contract-provenance gate it passed — are available through the API, along with company-level capability maps. Only edges at confidence ≥ 0.7 with evidence found verbatim in the source contract are published at all.

See plans →  ·  How the edges are graded →