For developers, integrators & POS partners

Build on the operating layer.

Fooodo exposes a REST API, webhook events, a typed contract for new POS connectors, and two MCP servers for AI clients — one for the public handbook, one per Insights tenant. The full reference is being prepared for general release; talk to engineering for early access against your specific integration.

Where you integrate

REST API

Read menus, push orders, query payment status, fetch reports. Token-authenticated. Documented per-endpoint with example payloads.

Webhooks

Order, payment and table-state events delivered to your endpoint. Signed payloads, retry on 5xx, idempotency keys.

POS connectors

A typed contract for new POS systems — Fooodo builds and operates the connector against your POS API. Implement nothing inside Fooodo; inherit payments, multi-tenancy and reporting. R-Keeper is the reference implementation.

Handbook MCP

An MCP endpoint at /api/mcp lets AI agents read the Fooodo handbook and submit lead requests on a buyer's behalf. Plug it into your editor or your own agent.

Insights MCP

A per-tenant MCP server exposes your operational analytics — period summaries, sales- and marketing-channel performance, product and per-restaurant performance, P&L, and three AI specialist agents — to any MCP-compatible client over OAuth 2.1. Dark by default; enable per org.

A concrete example

Push an order to Fooodo from your application. The order arrives in R-Keeper exactly as if a waiter had typed it in.

POST /api/v1/orders
curl -X POST https://api.fooodo.com/v1/orders \
  -H "Authorization: Bearer $FOOODO_TOKEN" \
  -H "Idempotency-Key: $(uuidgen)" \
  -d '{
    "table_id": "tbl_x7g2",
    "items": [
      { "product_id": "prod_pep_30", "qty": 2 },
      { "product_id": "prod_cola_05", "qty": 2 }
    ],
    "tip_amount_minor": 200,
    "payment": { "method": "card", "return_url": "https://your-app/return" }
  }'

What you can count on

  • Stable contracts — versioned, deprecated with notice, never silently broken
  • Idempotency keys on every write so retries don't duplicate orders
  • Webhook signatures so you can verify the source of every event
  • EU-hosted, GDPR-aligned, no third-country data residency surprises

Read the integration handbook

Architecture, order flows, R-Keeper integration, payments, the API reference and the POS vendor evaluation spec are all in the docs. The handbook is also exposed via MCP for AI clients.

Browse the docsPOS integration requirements

Talk to engineering

Tell us what you're building — POS connector, ordering integration, analytics export, AI agent against the MCP server. We'll match you with the right engineer and the right access tokens.

By submitting this form you agree to be contacted by Fooodo about your enquiry. We don't share your details with third parties. See our Privacy Notice for how we handle data.

Looking at Fooodo from a different angle? For restaurants · Partners · Insights · Security