Tips: Reading this article takes approximately 8 minutes
Introduction: The BookingMeta system has already achieved API integration with the Klook system for local activities, enabling automatic synchronization of orders from the Klook system to the BookingMeta system. Meanwhile, order operations in the BookingMeta system, such as completing a reservation, can also be automatically synchronized to the Klook system.
Note: Klook's airport transfer vehicle category is different from local activities and cannot be integrated via API for the time being. Local activities refer to items such as tickets, experiences, day tours, etc.
Main operation steps and content:
1.Contact Klook's BD, apply to open API docking, and make preparations;
2.Complete API testing in the testing environment;
3.Complete API testing in the production environment;
4.Formally implement API docking.
Preparatory Work
1 Contact the BD on Klook's side to apply for API connection
2 Complete API testing in the testing environment
3 Complete API testing in the production environment
3.1 Create a Klook agent with API connection method in the BookingMeta system
3.2 Create a test product within the BookingMeta system
You can use an existing product in the system, or create a new one for testing.
3.3 Provide relevant information to Klook
4. Formally Implement API Integration
After completing the test steps, the BD on the Klook side should allow the docking work for all official products to commence. Next, you need to complete two aspects of configuration, and then the sales orders on Klook can be successfully docked into the BookingMeta system. You can uniformly process and manage orders within the BookingMeta system.
4.1 Set Klook-side sales quotation
4.2 Provide product information for Klook's side
After completing the quotation settings, please provide Klook with a list of product information to be integrated (covering at least Product Code, BookingMeta SkuID, and Date Range Mapping information). The format of the information provided can follow Klook's requirements, such as in Excel format.
Note: otaId and secret remain unchanged in the production environment.