Bbot API
Bbot lives on as DoorDash Tableside Order & Pay with a public REST reference and staging host. API keys are emailed on request and shared over LastPass, the partner link is dead and the docs have not changed in four years.
Frequently asked questions
Bbot scores D on Supergood's API Report Card. Bbot lives on as DoorDash Tableside Order & Pay with a public REST reference and staging host. API keys are emailed on request and shared over LastPass, the partner link is dead and the docs have not changed in four years.
Without a usable official API, teams fall back on manual exports, file drops, or one-off vendor integrations. The other option is an unofficial API layer like Supergood that automates the authenticated web app directly. Site terms may apply to any integration approach, and how they apply is a determination each team makes for itself.
Bbot was a hospitality order-and-pay startup founded in 2017 that let guests scan a QR code to order and pay from a branded web menu, open shared tabs, and order ahead, with orders routed to tablets, printers or an integrated POS.
Restaurants & Food Service; bars, breweries, food halls, hotels, stadiums, bowling alleys and full-service restaurants that want QR ordering, tabs and pay-at-table without an app. Operators configure menus, location codes, fulfillment methods and QR signage in the Owner Panel, integrate their POS (Toast, Square, Revel, Deliverect and others) and loyalty (Thanx, Paytronix, Spendgo), and let guests scan to order, open tabs and pay from their phones.
DoorDash cites thousands of hospitality businesses on Tableside Order & Pay but publishes no location count, and the product is one niche module inside DoorDash's merchant suite rather than a category leader (https://merchants.doordash.com/en-us/products/tableside-order-and-pay).
Menus and pricing, orders and tabs, guest contact details for tabs and receipts, Stripe payment methods and checkout results, refunds, promo and loyalty redemptions, table and location configuration, POS integration settings and delivery details when DoorDash Drive is used.
Founded 2017; the API reference on ReadMe was last updated more than four years ago and predates the DoorDash acquisition, still pointing partners to meetbbot.com and engineering@bbot.menu contacts (https://bbot.readme.io/reference/webhook-endpoints).
Common alternatives include Toast, Square, GoTab, me&u, Sunday. Graded alternatives appear under "More from the report card" below.
Supergood's grades measure one thing: can a customer's engineering team get their own data out programmatically? Supergood checks six things (whether a real API exists, how access is gated, data coverage, auth quality, docs and developer experience, and stability) and rolls them into a letter grade. Supergood re-verifies grades, and they only move on evidence.
Not that we could find. There is no official Bbot MCP server in any public registry, and no maintained community server we're aware of. We re-verify this periodically — report an inaccuracy below if we missed one.
Not natively. Bbot doesn't publish an MCP server, so MCP clients like Claude, Cursor, and Codex have nothing to connect to out of the box. If that changes, this page will reflect it.