Kitchenhub App KitchenHub API

Name: KitchenHub API
Brand: KitchenHub API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentE CommerceOrder ManagementapiKey48 EndpointsREST

For Agents

Manage restaurant locations, stores, integration accounts, and webhook subscriptions inside a KitchenHub account from an automation or agent.

Install Jentic One Beta

Connect the KitchenHub API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the KitchenHub 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.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: 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

Step 2: 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 KitchenHub API.

Issue and refresh access and refresh tokens for the KitchenHub API

Create, read, update, and delete restaurant locations

Manage stores associated with each location

Subscribe webhooks to order and integration events

GET STARTED

Start building with KitchenHub API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI specification for KitchenHub API, keeping it validated and agent-ready. KitchenHub is a restaurant order-aggregation platform that connects locations and stores to delivery and ordering integrations, and the API exposes the location, store, webhook, integration-account, and provider model that drives those connections. The 48-endpoint surface includes a token issuance and refresh flow, full CRUD on locations and stores, configurable webhooks for order events, and a read-only providers endpoint that lists available integration partners. Authentication uses a Bearer token issued via the auth/token endpoints.

Use Cases

Patterns agents use KitchenHub API for, with concrete tasks.

★ Onboard a new restaurant location

When a brand opens a new site, an integration can call POST /v2/locations/ with the address and metadata, then POST /v2/stores/ to create the underlying store. The two-step flow gives the operator a clean separation between the physical location and the ordering surface attached to it.

POST a payload to /v2/locations/ with the address, then POST /v2/stores/ referencing the new location_id.

Webhook-driven order sync

Operators can subscribe to KitchenHub order events by calling POST /v2/webhooks/ with the destination URL and event types, then PATCH /v2/webhooks/{webhook_id}/ to adjust filters as the integration matures. The webhook delivers structured order events into the operator's order management system.

POST a webhook to /v2/webhooks/ with the order-events URL and confirm the subscription with GET /v2/webhooks/.

Integration provider rollout

Before enabling a new third-party ordering platform, an operator can call GET /v2/providers/ to confirm KitchenHub supports it, then POST /v2/integration_accounts/ to attach the store credentials. The pair of calls is enough to bring a new provider online for an existing location.

Call GET /v2/providers/, then POST /v2/integration_accounts/ with the chosen provider and the store credentials.

Token lifecycle management

Long-running integrations can call GET /v2/auth/token/validate/ before each batch and POST /v2/auth/token/refresh/ when the access token is close to expiry. This keeps the integration online without a full re-authentication round trip.

Call GET /v2/auth/token/validate/, and if invalid, POST /v2/auth/token/refresh/ with the refresh token.

Agent integration via Jentic

An ordering operations agent can use Jentic to discover the KitchenHub location and webhook operations, load their schemas, and execute them with vaulted credentials. The Bearer token lifecycle is handled inside Jentic, so the agent never reads the raw value.

Search Jentic for 'create a KitchenHub location', load POST /v2/locations/, and execute it with the new site's address.

Key Endpoints

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

METHOD

PATH

DESCRIPTION

POST

/v2/auth/token/

Create access and refresh tokens

POST

/v2/auth/token/refresh/

Refresh an access token

POST

/v2/locations/

Create a restaurant location

POST

/v2/stores/

Create a store under a location

POST

/v2/webhooks/

Create a webhook subscription

PATCH

/v2/webhooks/{webhook_id}/

Update a webhook

GET

/v2/providers/

List integration providers

POST

/v2/integration_accounts/

Create an integration account

POST

/v2/auth/token/

Create access and refresh tokens

POST

/v2/auth/token/refresh/

Refresh an access token

POST

/v2/locations/

Create a restaurant location

POST

/v2/stores/

Create a store under a location

POST

/v2/webhooks/

Create a webhook subscription

Why Jentic?

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

Credential isolation

KitchenHub long-lived credentials live in the Jentic vault. Jentic performs the auth/token issuance and refresh cycle, threading the Bearer token through subsequent calls so the agent never reads it.

Intent-based discovery

Agents search by intent, for example 'create a KitchenHub location' or 'subscribe to KitchenHub order events', and Jentic returns the matching POST operation with its full input schema.

Time to first call

Direct integration: 1 to 2 days for the token lifecycle, webhook handling, and resource hierarchy across 48 endpoints. Through Jentic: a few hours for the operations actually needed.

FAQs

Specific to using KitchenHub API through Jentic.

Why is there no official OpenAPI spec for KitchenHub API?

KitchenHub does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call KitchenHub 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 KitchenHub API use?

KitchenHub uses Bearer token authentication. Tokens are issued by POST /v2/auth/token/ and refreshed by POST /v2/auth/token/refresh/. Jentic stores the long-lived credentials in the vault and manages the token lifecycle internally.

Can I subscribe to order events with the KitchenHub API?

Yes. Call POST /v2/webhooks/ with a destination URL and the event types you want to receive. Use PATCH /v2/webhooks/{webhook_id}/ to adjust filters and DELETE /v2/webhooks/{webhook_id}/ to remove the subscription.

What are the rate limits for the KitchenHub API?

The OpenAPI specification does not declare explicit rate limits across the 48 endpoints. Validate the access token with GET /v2/auth/token/validate/ rather than refreshing on every request, and back off if the API returns a 429.

How do I create a KitchenHub location through Jentic?

Run pip install jentic, search Jentic for 'create a KitchenHub location', load the POST /v2/locations/ operation, and execute it with the site address. Jentic handles the Bearer token issuance and refresh cycle automatically.

Kitchenhub App KitchenHub API

Connect the KitchenHub API to your agent

Capabilities

Start building with KitchenHub API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs