Foodkit API

Name: Foodkit API API
Brand: Foodkit API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentE CommerceStorefrontnone34 EndpointsREST

For Agents

Drive a restaurant storefront through 34 Foodkit endpoints covering customer profiles, branch availability, menus, orders, quotes, loyalty, and referrals.

Connect the Foodkit API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Foodkit API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Install Jentic One Beta (Self-Hosted)

Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Foodkit API API.

Fetch the current menu and publications for a tenant via /v5/storefront/content/tenants/{tenant}/menu and /publications-cached

Check which branches can deliver to a given address via GET /v5/storefront/tenants/{tenant}/deliverable-branches

Submit a price quote and place an order via POST /v5/storefront/tenants/{tenant}/quotes and POST /v5/storefront/tenants/{tenant}/orders

GET STARTED

Start building with Foodkit API API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for Foodkit API, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for Foodkit API, keeping it validated and agent-ready. Foodkit is a white-label restaurant commerce platform that exposes storefront operations for customer profiles, branch availability, menus, orders, quotes, loyalty punch cards, and referrals. The 34 endpoints span versioned namespaces from v1 through v6 and are scoped per tenant and brand, so a single integration can drive multiple restaurant brands across iOS, Android, web, and kiosk surfaces. Use it to build the front-end of a delivery or pickup experience without operating a custom commerce backend.

Use Cases

Patterns agents use Foodkit API API for, with concrete tasks.

★ Branded delivery and pickup app

Power a restaurant brand's mobile app or website end-to-end with Foodkit. Customers register through /v1/storefront/customers, browse the menu loaded from /v5/storefront/content/tenants/{tenant}/menu, see which branches can deliver via /deliverable-branches, get a quote with /v5/storefront/tenants/{tenant}/quotes, and place an order with /v5/storefront/tenants/{tenant}/orders. Foodkit is multi-tenant and multi-brand, so one integration covers a portfolio of restaurant brands operating in different cities.

Load the menu for tenant t1 via GET /v5/storefront/content/tenants/t1/menu, build a basket of 2 items, POST /v5/storefront/tenants/t1/quotes for pricing, then POST /v5/storefront/tenants/t1/orders to place the order.

Loyalty and referrals concierge

Drive repeat orders by surfacing loyalty progress and referral status from Foodkit. GET /v6/storefront/loyalty/tenants/{tenant}/customers/{customer}/punch-card returns the customer's punch card state and GET /v6/storefront/referrals/tenants/{tenant}/customers/{customer} returns referral rewards earned. Surface these in the app's account screen or as nudges in checkout to lift conversion without a separate loyalty platform.

GET /v6/storefront/loyalty/tenants/t1/customers/c123/punch-card and render the current stamps and reward threshold in the app account screen.

Order tracking and post-purchase updates

After an order is placed, hit GET /v4/storefront/customers/brands/{brand}/customers/{customer}/orders/{id}/track to retrieve the live state of the order through preparation, dispatch, and delivery. Combine with GET /v3/storefront/customers/me/orders to render an order history view. This gives a customer-facing app real-time visibility without polling the underlying POS system directly.

GET /v4/storefront/customers/brands/b1/customers/c123/orders/o789/track and parse the state field to render a status bar.

Agent-driven storefront automation

An AI assistant inside a restaurant brand's customer support tool can resolve order, menu, and loyalty questions by calling Foodkit through Jentic. The agent searches by intent, gets the right tenant-scoped operation, and runs it on behalf of the support agent without ever holding raw credentials or learning Foodkit's URL conventions.

Through Jentic, search 'track a restaurant order', load the Foodkit /v4/.../orders/{id}/track operation, and execute with the customer's brand, customer, and order id.

Key Endpoints

34 endpoints — jentic publishes the only available openapi specification for foodkit api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/v5/storefront/content/tenants/{tenant}/menu

Fetch the current menu for a tenant

GET

/v5/storefront/tenants/{tenant}/deliverable-branches

List branches that can deliver to a location

POST

/v5/storefront/tenants/{tenant}/quotes

Quote a basket with pricing and fees

POST

/v5/storefront/tenants/{tenant}/orders

Place an order

GET

/v4/storefront/customers/brands/{brand}/customers/{customer}/orders/{id}/track

Track the state of a placed order

GET

/v6/storefront/loyalty/tenants/{tenant}/customers/{customer}/punch-card

Read a customer's loyalty punch card

POST

/v1/storefront/customers

GET

/v5/storefront/content/tenants/{tenant}/menu

Fetch the current menu for a tenant

GET

/v5/storefront/tenants/{tenant}/deliverable-branches

List branches that can deliver to a location

POST

/v5/storefront/tenants/{tenant}/quotes

Quote a basket with pricing and fees

POST

/v5/storefront/tenants/{tenant}/orders

Place an order

GET

/v4/storefront/customers/brands/{brand}/customers/{customer}/orders/{id}/track

Track the state of a placed order

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Tenant-scoped Foodkit credentials are stored encrypted in the Jentic vault. Agents call operations through scoped Jentic tokens and Foodkit headers are added at execution, so the raw credential never reaches the agent.

Intent-based discovery

Agents search by intent (e.g., 'place a restaurant order' or 'fetch a restaurant menu') and Jentic returns the right Foodkit storefront operations with their tenant and brand parameters resolved.

Time to first call

Direct Foodkit integration takes several days to wire up tenant-scoped paths, quote-then-order flows, and order tracking. Through Jentic the same flow is executable in under an hour.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Toast

Restaurant POS and ordering platform with broader operations coverage.

Choose Toast when the integration also needs in-restaurant POS and kitchen operations beyond storefront ordering.

Alternative

Square

Commerce APIs covering catalog, orders, and in-person payments.

Choose Square when the project needs unified online and POS payments alongside ordering and the brand is not committed to a white-label restaurant platform.

Complementary

Stripe

Payments, subscriptions, and refund APIs.

Use Stripe alongside Foodkit when the storefront needs to accept card or wallet payments at checkout — Foodkit handles ordering, Stripe handles the money movement.

FAQs

Specific to using Foodkit API API through Jentic.

Why is there no official OpenAPI spec for Foodkit API?

Foodkit does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Foodkit API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Foodkit API use?

The Foodkit storefront spec does not declare a security scheme on its endpoints; in practice Foodkit issues tenant-scoped credentials negotiated with their team for production use. Through Jentic, any provisioned credential is held in the vault and injected at call time, so the raw value never reaches the agent.

Can I place an order with the Foodkit API through Jentic?

Yes. Build the basket against the menu returned by /v5/storefront/content/tenants/{tenant}/menu, call POST /v5/storefront/tenants/{tenant}/quotes for pricing, and then POST /v5/storefront/tenants/{tenant}/orders to commit the order. Through Jentic, search 'place a Foodkit order' to load the operation schemas in sequence.

How do I check whether a branch delivers to a given address with the Foodkit API?

Call GET /v5/storefront/tenants/{tenant}/deliverable-branches with the location parameters. For brand-scoped checks, use /v5/storefront/tenants/{tenant}/brands/{brand}/deliverable-branches. The response identifies the branches available for the given address.

What are the rate limits for the Foodkit API?

The OpenAPI spec does not declare rate limits. Foodkit applies tenant-level throughput limits negotiated with their team; treat HTTP 429 as a signal to back off and contact Foodkit support for production volume.

How do I read a customer's loyalty status with the Foodkit API?

Use GET /v6/storefront/loyalty/tenants/{tenant}/customers/{customer}/punch-card to retrieve the per-customer punch card state, and /v6/storefront/loyalty/tenants/{tenant}/punch-card for the punch card configuration of the tenant. The two combined give you progress against the reward threshold.