Earlier this week we introduced the new Fresh KDS API, a read-only way for enterprise IT teams and technology partners to pull their own location's kitchen performance data into other systems. Here's what it actually covers today, what it doesn't, and how to get access.

What's available today

The API is read-only and scoped to the locations a given request has access to. It exposes the same kind of kitchen performance metrics operators already see inside Fresh KDS: things like on-time performance, station-level delay, and prep time, built from the order activity Fresh KDS captures at the point of production.

This is meant to answer a specific question well: how is this kitchen actually performing? It's not a general-purpose data export of everything Fresh KDS knows.

What's out of scope for now

A few things are intentionally not part of this first version.

There's no write access. The API can't be used to send data into Fresh KDS or change anything about how a kitchen or screen is configured.

There's no vendor-on-behalf access. Access is scoped to a location's own data, requested by that location's own team or an authorized partner, not a third party acting on a restaurant's behalf without direct authorization.

There are no real-time event streams. The API returns performance data, not a live feed of every order as it happens.

None of these are permanent limits. They're where we drew the line for a first version we could ship responsibly, and they're the kind of thing that can expand as we learn what teams actually need.

How to request access

Access is available to two groups: enterprise IT teams managing Fresh KDS across multiple locations, and technology partners building products that use real kitchen performance data.

To get started, reach out through our enterprise page at fresh.technology/kds/enterprise. We'll walk through what your team or product needs, confirm the right scope of access, and get you set up with documentation.

The honest version

This is a first version. It covers a specific, useful slice of what Fresh KDS knows about a kitchen, not everything. If your team needs something the API doesn't support yet, tell us. That's exactly the kind of feedback that shapes what comes next.