Contact TouchBistro Point of Sale support to request API credentials; TouchBistro does not offer self-service API key generation and credentials are issued upon request
Share the issued credentials with your online ordering integration partner or middleware (for example, Deliverect, UrbanPiper, or a direct integration) as required by the integration pattern
Configure the integration on the TouchBistro side by mapping the online ordering platform's menu items and modifiers to corresponding TouchBistro menu items using the POS identifiers provided in the TouchBistro back-office
Test order injection by placing a test order from the online ordering platform and verifying it appears on the TouchBistro POS with the correct items, modifiers, fulfillment type, and pricing
Confirm that order status updates (accepted, ready, completed) flow back to the ordering platform if the integration supports bidirectional status communication
Monitor the live integration for order injection errors and establish an alert threshold for failures; TouchBistro does not have a native public developer portal, so integration support goes through their support team
Known gotchas
TouchBistro's API is not publicly documented in a self-service developer portal; all API credential requests and integration support are handled through TouchBistro support, which adds lead time
Menu item mapping between the ordering platform and TouchBistro must be maintained manually or via a middleware layer; mismatched PLU codes or item IDs cause silent injection failures
POS integrations are listed as free with TouchBistro but some integration partners charge independently; clarify billing with the middleware or ordering platform before going live
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp