Guest & Traveller Management

BC-4040 Level 1 Travel & Hospitality 10 providers 17 API surfaces 2 rated strong or better

Stewardship of the single guest and traveller record across the enterprise — identity, preferences, consent, recognition, segmentation, and travel-document/compliance data — independent of any single channel or property.

Guest & Traveller Management (BC-4040) is a level-1 business capability in the Travel & Hospitality model. The catalog holds 17 API surface(s) from 10 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

Guest Profile & Identity Management BC-4040.10

Creation, deduplication, and identity verification of the single guest profile across booking and operational systems.

9 providers, 11 API surfaces

Guest Preference & Personalisation Management BC-4040.20

Capture and stewardship of guest preferences covering stay, dietary, and accessibility requirements, plus personalisation rules.

no catalog coverage

Guest Consent & Privacy Management BC-4040.30

Management of guest consent, marketing permission, data subject rights, and cross-border transfer compliance across travel data.

no catalog coverage

Guest Recognition & Tier Status Delivery BC-4040.40

Delivery of recognition signals and tier status to operational teams so guests are recognised consistently across touchpoints.

no catalog coverage

Guest Segmentation & Insight Management BC-4040.50

Definition of guest segments, modelling of lifetime value and churn, and generation of cohort and behavioural insight.

no catalog coverage

Traveller Document & Compliance Data Management BC-4040.60

Management of travel-document, APIS, visa, and watchlist data required to satisfy carriage and border-control obligations.

3 providers, 6 API surfaces

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
Oracle HospitalityProfileProfileExternal2 APIs73.4
Strong 1 Solid coverage with minor gaps
MewsAccountsCustomersIdentity documents3 APIs60.1
Developing 2 Usable, with meaningful gaps to close
TUI GroupapisMessagedocumentspersonsverifiedTravelDocuments5 APIs53.0GuestReadyguest_registration1 API43.4
Thin 6 Limited public surface area
Eat AppConcierge - Guests1 API38.4OwnerRezGuests1 API36.1SmoobuGuests1 API34.9GuestyGuests1 API33.8TableCheckcustomers1 API32.5CloudbedsGetGuestList1 API31.1

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 Guest & Traveller 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 →