使用EPS_EXT_ProfileSearchRQ API无法获取企业关联旅行者TPA_Identities问题咨询

Let's break down why your request isn't returning the traveler profile references (TPA_Identities) linked to your corporate profile, and fix the issues step by step:

1. Incorrect ProfileTypeCode for your use case #

You set ProfileTypeCode="TVL" in your request, but this targets traveler profiles directly, not the travelers associated with a corporate profile. To get traveler references under a specific corporate profile, you first need to target the corporate profile itself by using ProfileTypeCode="COR".

2. Missing IncludeAssociatedProfiles="Y" parameter #

This is the critical missing piece! The ProfileSearchCriteria element requires the IncludeAssociatedProfiles="Y" flag to tell the API to return child profiles (travelers) linked to the parent corporate profile. Without this, the API only returns the top-level profile you searched for, not its associated records.

3. Ambiguous profile targeting with only ProfileName #

Using just ProfileName="COMPANY NAME" can lead to inconsistent results, especially if multiple profiles share the same name. For precise targeting, include the corporate profile's UniqueID in the TPA_Identity element (you can get this from a prior corporate profile search or lookup).

Corrected Request Example #

Here's how to adjust your request to retrieve the linked traveler TPA_Identities:

<?xml version="1.0" encoding="utf-16"?>
<Sabre_OTA_ProfileSearchRQ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" Version="6.46" ReturnPaymentCardToken="Y">
  <ProfileSearchCriteria ProfileNameOnly="N" ReturnCount="250" IncludeAssociatedProfiles="Y" xmlns="http://www.sabre.com/eps/schemas">
    <!-- Target the corporate profile with correct type and unique ID -->
    <TPA_Identity ProfileTypeCode="COR" ClientCode="TN" ClientContextCode="TMP" ProfileName="COMPANY NAME" DomainID="XX12" UniqueID="YOUR_CORPORATE_PROFILE_UNIQUE_ID" />
    <CustomerReferenceInfo />
  </ProfileSearchCriteria>
</Sabre_OTA_ProfileSearchRQ>

Key Changes Explained: #

• Switched ProfileTypeCode to "COR" to target the corporate parent profile
• Added IncludeAssociatedProfiles="Y" to enable retrieval of linked traveler profiles
• Changed ProfileNameOnly="N" to allow more precise matching (and added UniqueID for accuracy)

With this request, the API response should include the corporate profile plus a list of associated traveler profiles under the AssociatedProfiles section, each containing their TPA_Identity details.

内容的提问来源于stack exchange，提问作者drtrobridge