As part of our design update, the screenshots are currently being revised.

TABLE OF CONTENTS

'corpCode' is an attribute that can be included in the request body when sending availability requests to Availability and Livecheck APIs. 

A corpCode is assigned to each corporate account that a TMC/booking platform owns and indicates the using party of the negotitated rates.  


A corpCode is mapped with the TMC/ booking platform, a supplier and the rate plan Id that a supplier uses to distribute the negotiated rates. 


When a TMC sends a query to Availability/ Livecheck APIs with ‘corpCode' in the request body, the system will filter the hotel offers that only this corporate account is allowed to access in hotel CRS system.  The hotel offers include corporate negotiated rates (RFP rates), consortia rates and rack rates. 



Frequently Asked Questions

Q1: Do you have any validation of corpCodes passed through API requests? 

A1: corpCode supports alphabet, numeric characters up to 20 characters, and it is case-sensative. 


Q2: Do you support multiple corpCodes passed through API requests? 

A2: Currently we do not support this.


Q3: How are chain-wide discount rates being recognized in your system? Through which parameter do we send the consortia rate identifyer? 

A3: The chain-wide discount rates are tagged as “CWD” in the attribute of rateFlag which is returned in the response body of Hotel, Availability, Livecheck API. 


Q4: What is the difference between the paramters ‘corpCode' and  'corpAccount' in the request and response? 

A4: ‘corpCode' is used by TMC/ booking platform to identify who are the requesting customer to determine which product offers can be accessed and returned in the response. 'corpAccount' is an attribute to be used when the supplier requests the distributor to pass a specific value for identifying who is requesting.  


corpAccount has 2 keys, corpProgramCode and corpId. If the ‘corpAccount’ is not present in the request, BTS system checks the mapping of the corpCode and the productCandidate, and if the mapping exists in BTS system, the matched value will be sent as corpAccount to the supplier’s system. 



Troubleshooting 

  1. The system returns an error: corpCode not found
    The corpCode present in the API request is not validated by BTS system. Please contact [email protected] for support.

  2. The system returns an error: corpCode inactive
    The corpCode present in the API request is inactive in BTS system. Please contact [email protected] for support.

  3. The system returns an error: corpCode not activated for the current supplier
    The corpCode present in the API request is not activated for the supplier specified. Please make sure you use a correct corpCode, or contact [email protected] to activate the corpCode.

  4. The response returned includes empty data in the ‘productCandidate’
    This might be due to that the productCandidate is not found after matching the existing rules that are associated with the corpCode and distributor ID, supplier ID present in the API request.