Abstract: A trip-planning operation includes identifying a primary work location associated with each user account of a dependency graph defined by the three or more users performing a set of interaction events on a software platform. A first set of advanced programming interface (API) calls is generated to a third party service to obtain one or more query results based on the primary work location, which are then analyzed to determine a ranked list of candidate trip locations based on a ranking criterion. At least a portion of the ranked list is displayed on the client device and, in response to an input from the client device and upon a determination that a consensus regarding the candidate trip location exists among the three or more user accounts, a second API call is generated to the third party service to book a trip to the candidate trip location for each user account.

Abstract: A trip-planning operation includes identifying a primary work location associated with each user account of a dependency graph defined by the three or more users performing a set of interaction events on a software platform. A first set of advanced programming interface (API) calls is generated to a third party service to obtain one or more query results based on the primary work location, which are then analyzed to determine a ranked list of candidate trip locations based on a ranking criterion. At least a portion of the ranked list is displayed on the client device and, in response to an input from the client device and upon a determination that a consensus regarding the candidate trip location exists among the three or more user accounts, a second API call is generated to the third party service to book a trip to the candidate trip location for each user account.