3814782 - Why is the travel profile data not syncing using the Concur Travel Profile API?

API synchronization (sync) is a process where data is exchanged between two systems in real-time or at scheduled intervals, ensuring consistency between them. In the context of SAP Concur, API sync is used to transfer data like user profiles, bookings, expense information, and other system-critical data between Concur and external systems such as travel management companies (TMCs), global distribution systems (GDSs), or HR platforms.
 

SAP Concur Travel Profile Sync Overview for Travel Profile API 2.0 method

1. Sync Flow

• When a user profile is created or updated in SAP Concur Travel, the Travel Management Company's (TMC) profile application sends a request to the Concur Travel Profile API to retrieve the user data.
• The API then responds back to the TMC's application with the data requested. Note: The API works by request only. This means the API will never pull data from any application without a request first being sent from the TMC. 
• The profile can also be created/updated in the TMC's profile application and sent to Concur via the API, but only if the application is programmed to sends the request. 
• From there, the TMC processes the profile and forwards it to the Global Distribution System (GDS), where it is stored for travel bookings.
  • Please note that travel agencies often have their own internal programming to review the profile data received via the API. If the TMC has specific profile requirements built into its application, errors may occur after the data is received. In those cases, the TMC must review for errors and make corrections where needed, as SAP Concur does not have access to the TMC’s internal application.  

2. PAR Level Field

• Once the profile has been successfully synced to the travel agency’s reservation system (GDS) from their agency's profile application, the agency can then choose to send a request via the API to add the PAR Level field with the profile name from the GDS (as well as the Sabre ID if the GDS is Sabre).
  • Exception: Some TMC's prefer not to populate the PAR Level 2 Star field. This ultimately depends on how the travel agency wants Concur to create the PNR in the GDS for online bookings. If the PAR Level 2 Star field is left blank, Concur’s programming will manually build the PNR instead. For more information on this process, please refer to the following KB article - "What is Manual Build in Concur Travel? ?"
    • If the PNR is manually built, it is the TMC’s responsibility to ensure that any specific data elements required in the PNR for their back-office accounting or invoicing processes are added either through the Concur Finishing Template, and/or through their own quality control (QC) automation.

3. Error Logs and Troubleshoot

• Profile sync via API is a request/response process
• SAP Concur Support can typically confirm whether the request was sent/received successfully and what high-level response status was returned (for example, a 200 success response) within the last 30 days. 
• However, SAP Concur does not have visibility into how the travel agency’s application processes, stores, maps, or handles the data after it is received successfully.
• Because SAP Concur does not have access to the TMC’s internal system or application logs, we rely on the travel agency to provide the full API request and response details from their side when deeper investigation is needed.
• To know what required information is needed from the TMC for Travel Support to further investigate see KB Article - What information is required to open a Travel Profile API 2.0 case?

The company configuration uses Travel Profile API 2.0 to sync traveler profile data to the TMC profile application, but the profile data is not syncing. , KBA , CON-CA-USP , User Profile , Problem