The provided diagram visually outlines the API endpoints available in cupid, categorized into four main sections: Hotel Data API, Room Map API, and Room Match API.
Endpoints breakdown
Room Match API:
- Reference Room Match:
POST /ref_room_match: Match rooms with cupid's data as reference.
- Room Match:
POST /room_match: Providing reference and input catalogs to match the rooms.POST /bulk_room_match: Providing multiple reference and input catalogs to match the rooms.
Room Map API:
- Room Map:
POST /room_map: Consolidates and groups similar rooms from multiple suppliers for a given property.
- Room Sub
POST /room_sub: Facilitates room target matching by identifying exact matches or upgraded rooms for a specified target room.
Hotel Content API:
- Hotel Content:
GET /property: Returns all the static contents details of a hotel or property if the hotel ID is provided
- Hotel Review:
GET /property/reviews: Returns all the reviews for a specific hotel or property.
- Hotel Translation
GET /property/{propertyId}/lang/{lang}: Returns all the translated static contents details of a hotel or property if the hotel ID is provided
This structured layout facilitates easy navigation and use of the API for tasks ranging from fetching basic hotel data to managing room mapping and matching.
Open API Specifications
- Room Match: https://docs.cupid.travel/openapi/64be1f38dc664c007400ecb0
- Room Mapping: https://docs.cupid.travel/openapi/65f9bb3719b05100317a6c36
- Hotel Content: https://docs.cupid.travel/openapi/65f9bb6f05207c00296bc7a3