Flipdish API

Name: Flipdish API
Brand: Flipdish API
Availability: InStock

✓ Official Vendor SpecE CommerceStorefrontoauth249 EndpointsREST

For Agents

Manage Flipdish brands, restaurant properties, sales channels, menus, opening hours, and webhooks for online ordering operations.

Install Jentic One Beta

Connect the Flipdish API to your agent

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

Create and update organizations, brands, and individual restaurant properties

Publish or unpublish sales channels for web, app, and kiosk ordering on a per-property basis

Manage versioned menus and roll out changes by promoting a draft menu to current

GET STARTED

Start building with Flipdish API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Flipdish API for, with concrete tasks.

★ Multi-location menu rollout

Restaurant chains use the menu management endpoints to promote a draft menu to current for individual properties or for an entire brand. The /menumanagement/orgs/{orgId}/menus/{menuId}/current endpoint controls which version is live, and snoozes pause specific items at a single property without editing the master menu. This supports coordinated rollouts where a new menu launches at one location ahead of others.

Promote draft menu M42 to current for the Dublin property and snooze item ID 99 for the next 4 hours

Restaurant property and channel onboarding

Operations teams onboard new restaurant locations by creating a property under an existing brand, configuring opening hours and VAT, and publishing sales channels for web, app, and kiosk ordering. The /orgManagement/orgs/{orgId}/properties endpoints handle the property lifecycle, while the salesChannels sub-resource publishes or archives each ordering surface.

Create a new property under brand B12 with opening hours and VAT, then publish web and app sales channels

Order webhook integration

Restaurant ops platforms register webhooks against the Flipdish API to receive order events as they happen, then route them into kitchen displays, delivery dispatch, and analytics dashboards. The Webhooks tag exposes registration and management endpoints so subscriptions can be added, paused, or rotated when secrets change.

AI agent restaurant operations assistant

An AI ops agent uses Flipdish through Jentic to react to live operating decisions: snoozing menu items when stock runs out, adjusting opening hours when a kitchen closes early, and listing audit-log entries when staff want to know who made a change. Jentic returns the right Flipdish operation per intent across the 49-endpoint surface.

Snooze menu item ID 504 across all properties of brand B7 until 23:00 tonight and post the audit log of all snoozes today

Key Endpoints

49 endpoints — the flipdish api powers the flipdish online ordering platform for restaurant and quick-service brands.

METHOD

PATH

DESCRIPTION

POST

/orgManagement/orgs/{orgId}/properties

Create a new restaurant property

POST

/orgManagement/orgs/{orgId}/properties/{propertyId}/salesChannels/{salesChannelId}/publish

Publish a sales channel for a property

GET

/menumanagement/orgs/{orgId}/menus/published

List published menus

POST

/menumanagement/orgs/{orgId}/menus/{menuId}/current

Promote a menu version to current

POST

/menumanagement/orgs/{orgId}/menus/{menuId}/snoozes

Snooze a menu item temporarily

PUT

/orgManagement/orgs/{orgId}/properties/{propertyId}/openingHours

Update property opening hours

PUT

/orgManagement/orgs/{orgId}/properties/{propertyId}/vat

Update VAT settings for a property

POST

/orgManagement/orgs/{orgId}/properties

Create a new restaurant property

POST

/orgManagement/orgs/{orgId}/properties/{propertyId}/salesChannels/{salesChannelId}/publish

Publish a sales channel for a property

GET

/menumanagement/orgs/{orgId}/menus/published

List published menus

POST

/menumanagement/orgs/{orgId}/menus/{menuId}/current

Promote a menu version to current

POST

/menumanagement/orgs/{orgId}/menus/{menuId}/snoozes

Snooze a menu item temporarily

Why Jentic?

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

Credential isolation

Flipdish OAuth 2.0 client credentials are stored encrypted in the Jentic vault. Agents receive scoped access tokens at execution time, so client secrets never enter the agent context.

Intent-based discovery

Agents search Jentic by intent such as 'snooze a menu item' and Jentic returns the matching Flipdish operation with its input schema, so the agent does not need to navigate the orgManagement and menumanagement path hierarchies manually.

Time to first call

Direct Flipdish integration: 3-5 days for OAuth setup, multi-tenant org/brand/property handling, and webhook security. Through Jentic: under 1 hour to search, load the schema, and execute.

FAQs

Specific to using Flipdish API through Jentic.

What authentication does the Flipdish API use?

The Flipdish API uses OAuth 2.0. Through Jentic, the OAuth client credentials are stored in the encrypted vault and exchanged for short-lived access tokens at execution time.

Can I snooze a menu item with the Flipdish API?

Yes. POST to /menumanagement/orgs/{orgId}/menus/{menuId}/snoozes to mark an item as temporarily unavailable, and call /menumanagement/orgs/{orgId}/menus/{menuId}/un-snoozes to bring it back.

How do I publish a new menu to a single restaurant property?

Promote the menu version using POST /menumanagement/orgs/{orgId}/menus/{menuId}/current scoped to the target property, then publish the relevant sales channels with /orgManagement/orgs/{orgId}/properties/{propertyId}/salesChannels/{salesChannelId}/publish.

What are the rate limits for the Flipdish API?

Flipdish does not document a fixed rate limit in the spec. Limits are applied per organization and per token. Treat 429 responses as the source of truth and back off using the Retry-After header.

How do I publish a sales channel through Jentic?

Search Jentic for 'publish a Flipdish sales channel', load the schema for /orgManagement/orgs/{orgId}/properties/{propertyId}/salesChannels/{salesChannelId}/publish, and execute. Install with pip install jentic and sign up at https://app.jentic.com/sign-up.

Can I receive order events as webhooks?

Yes. The Webhooks endpoints register and manage subscriptions for events such as new orders and menu updates, with the subscription secret rotated through the same endpoints.

Flipdish API

Connect the Flipdish API to your agent

Capabilities

Start building with Flipdish API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs