Intro
The Kitchenhub API is tailored to address the challenges of integrating your enterprise with numerous systems prevalent in the restaurant sector. It also tackles the inaccessibility of these systems for medium and small-scale businesses in the industry.
Our core service revolves around integrating with leading U.S. marketplaces like Doordash, GrubHub, UberEats, and more. Beyond these, we support a range of other popular restaurant services, including ChowNow, Flipdish, Menufy, and GloriaFood, among others. For a comprehensive, current list of services compatible with our API, please refer here.
A unique aspect of our offering is the flexibility to select specific API components for integration. This feature not only eases the integration process but also empowers you to evolve your product step by step.
How to get an access to the API
Unfortunately, our API is not open. Our team strives to help partners at all stages of integration. From concept discussions to pilot launch.
This means that we can't connect with a large number of customers at the same time, otherwise, the quality of our support will drop.
If you are still interested in integration please leave your request, we will contact you to clarify why you need integration and what action plan you need to follow to start integration.
API components
The KitchenHub API suite comprises:
Locations and stores API
The Locations and Stores API structures objects to mirror real restaurants and their representation in our integrated systems.
Order API
This allows access to orders from linked providers using webhook notifications and pooling methods.
Provider API: This facilitates connections to marketplaces or online order services for stores and handles their availability.
Integrations API
This aids in the onboarding, management, and listing of merchant integrations with external services. It also manages temporary states like pause or resume.
Menu API
This provides a platform to set up and manage menus, items, modifiers, and their availability.
Which API Should You Choose?
It depends on the capabilities of your service, as well as scenarios for using integrations. Let's describe the main ones.
Scenario 1: Order Reception and Management.
This is the most straightforward scenario to set up, typically taking 2-3 weeks. It's ideal for a pilot project or proof of concept. If you'd like to centralize all marketplace operations (like menus and connectivity) within Kitchenhub and solely manage orders on your platform, this is your best bet.
Scenario 2: Observing Orders in Parallel.
If your goal is to view orders in your system without necessarily confirming them, this scenario is for you. It's particularly beneficial for businesses specializing in order logistics. Our platform can seamlessly connect to multiple renowned marketplaces simultaneously. This ensures restaurants can maintain their regular order processes, whether through tablets or POS integrations, without any disruptions.
Scenario 3: Synchronizing Orders and Menus.
If your system requires an order to be linked to a specific menu and you can't generate one without this linkage, you'll need integrations for both. This is a common requirement for POS systems. Here, you'd upload menus (featuring item IDs from your system), and we'd then reconfigure a merchant's menu in the connected services based on the provided menu. Once this is accomplished, you'll begin receiving orders that align with your menu.