Food Delivery Domain

Food Delivery API

Restaurants, menus, cuisine categories, and delivery tracking

API Prefix

/api/food

Every endpoint hangs off this prefix so you can compose requests consistently.

Endpoint coverage

8

Curated routes spanning common workflows

Playground ready

Deep link directly into the playground with your preferred method and path.

Open in Playground

Capabilities

What you can simulate

Mix and match endpoints to validate dashboards, onboarding flows, error states, and integration docs before touching production systems.

1

Restaurant cards with delivery windows and fees

2

Menu categories and item customisations

3

Cuisine category discovery endpoints

4

Order creation and deterministic tracking flows

5

Driver, ETA, and status timeline payloads

6

Filters for open now, cuisine, and rating

Endpoints

Available routes

Each endpoint responds with JSON objects modeled after production systems, complete with pagination, filtering, and optional latency controls for stress testing.

GET

/api/food/restaurants

Try it
GET

/api/food/restaurants?q=burger&open_now=true

Try it
GET

/api/food/restaurants/rest_001

Try it
GET

/api/food/restaurants/rest_001/menu

Try it
GET

/api/food/categories

Try it
POST

/api/food/orders

Try it
GET

/api/food/orders/order_mock_001

Try it
GET

/api/food/orders/order_mock_001/tracking

Try it
food

Ship food delivery demos faster

Prototype ordering, checkout, and tracking flows without inventing your own restaurant dataset.

Explore more

Other mock API domains

Browse the full library of free mock API domains for your next project.