Japan

Japan Food Data API: Uber Eats, Demae-can and Restaurant Menu Data

FoodSpark’s Japan food data API delivers restaurant, menu, and delivery data from Uber Eats, Demae-can, and Rocket Now. You can then get it as JSON, CSV, or a live API feed. Every record also carries the prefecture, city and postal code, so you can compare Tokyo, Osaka and Fukuoka fairly.

In short, you get:

• Delivery app data: restaurants, menus, prices, fees, offers and ratings
• Menu details: dishes, sets, sizes, add-ons and allergen notes
• Japan-ready fields: tax rate, tax-inclusive prices, in-store price flags and seven-digit postal codes
• Flexible delivery: a one-off dataset, a scheduled feed or live API access

Why the Japan Food Data API Needs Local Detail

Japan’s delivery market, however, has its own tax rules, pricing habits, and labels. So, data that ignores them leads to unfair comparisons. That is why our Japan food data API captures each local detail as its own field.

• A mature market: Food delivery in Japan reached ¥824.0 billion in 2025, up just 2.0%. Meanwhile, apps now compete harder on price.
• Clear leader: Uber Eats has served all 47 prefectures since 2021. In late 2024, it also had 46% of delivery-app monthly users.
• Store-price menus: In March 2026, both Uber Eats and Demae-can began programmes that match in-store prices. So we flag which listings charge the same as the shop.
• Two tax rates: Takeout and delivery food carry 8% consumption tax, while dine-in meals and alcohol carry 10%. In addition, prices shown to shoppers must include tax.
• Fewer apps: Wolt left Japan on March 4, 2026, and KDDI closed its menu on September 30, 2026. Meanwhile, Coupang’s Rocket Now passed 10,000 restaurants.

Japan Food Data API at a Glance

Sources Covered by the Japan Food Data API

The Japan Food Data API collects public data from the apps and chains Japanese diners use most. Then we merge it into one clean dataset. Each linked name also opens its full API page.

Delivery Apps

So why not use the apps’ own APIs? Uber Eats and Demae-can do offer tools, but only to their restaurant partners. However, those tools show your own stores and orders. By contrast, the Japan food data API shows the whole market in the postal codes you choose.

Restaurant Chains

Chains: we also cover chains such as McDonald’s, Starbucks and Domino’s. For example, McDonald’s Japan ran 3,047 stores at the end of September 2026. Similarly, Sukiya runs about 2,000 gyudon restaurants, which we can add on request.

Need a source that is not listed? Then we build a custom crawler and add it to your Japan food data API feed.

Data Fields in the Japan Food Data API

Every Japan food data API record uses the same clean field names. As a result, you can join Uber Eats, Demae-can and Rocket Now data without extra work.

Restaurant and Menu Fields

Fee and Offer Fields

Japan-Only Extras

• Tax rate: 8% for delivery food or 10% for alcohol, per item
• Store-price flag: shows whether a listing matches its in-store price
• Allergen notes: any allergen information a menu chooses to show
• Local text: dish names stay in Japanese, while an English category is optional

Cities and Prefectures in the Japan Food Data API

The Japan Food Data API covers every area a source app serves. Even so, the big cities matter most, since most apps compete there.

For example, you can compare one ramen chain’s prices in Tokyo and Fukuoka. Likewise, you can check how delivery fees change from ward to ward.

How the Japan Food Data API Maps Postal Codes

Japanese postal codes have seven digits, written as 100-0001. Then the Japan Food Data API adds the prefecture, city, ward, and coordinates to each record. As a result, you can roll data up from one street to all 47 prefectures.

Sample Record From the Japan Food Data API

Below, for example, is a shortened record from the Japan Food Data API. The restaurant and values are examples only.

{
  "platform": "ubereats_jp",
  "restaurant_id": "ue_jp_418822",
  "restaurant_name": "サンプルラーメン",
  "restaurant_name_en": "Sample Ramen",
  "prefecture": "Tokyo",
  "city": "Shibuya-ku",
  "postal_code": "150-0002",
  "item_name": "醤油ラーメン",
  "item_name_en": "Shoyu ramen",
  "item_price_jpy": 980,
  "tax_included": true,
  "tax_rate": 0.08,
  "store_price_match": true,
  "delivery_fee_jpy": 150,
  "rating": 4.6,
  "delivery_time_min": "20-30",
  "collected_at": "2026-10-07T19:00:00+09:00"
}

Formats and Delivery

You can get the data as JSON, CSV, Excel, or XML. In addition, we can push it to a database, cloud storage, or your own endpoint. Refresh rates, meanwhile, range from real-time and daily to weekly or monthly.

How It Works

1. Share your needs: tell us the apps, cities, and fields you want.
2. Review a sample: check a free Japan sample first.
3. Set up the feed: then we configure crawlers, schedules, and quality checks.
4. Stay covered: finally, we fix the crawlers whenever an app changes.

What Teams Do With the Japan Food Data API

Teams use the Japan Food Data API to follow a mature market where price competition is growing. For example, they:

1. Compare platforms: check the same restaurant’s price on Uber Eats, Demae-can and Rocket Now.
2. Track store-price menus: see which restaurants now charge in-store prices on each app.
3. Watch the tax change: follow menu prices if the food tax rate drops in 2027.
4. Benchmark chains: compare McDonald’s, Sukiya and other chain prices by prefecture.
5. Plan expansion: compare restaurant counts and fees by city before you launch.
6. Feed AI and dashboards: use fresh, structured data instead of reports that go stale.

Because prices, fees, and apps keep shifting, a one-off report ages fast. So a scheduled feed usually works better.

Japan Food Data API: FAQs

What is a Japan food data API?

A Japan food data API gives your software structured data from Japanese delivery apps and restaurants. For example, it includes menus, prices, fees, offers, and ratings. So your apps and dashboards always work with fresh data.

Can you extract Uber Eats Japan and Demae-can data?

Yes. We collect public Uber Eats and Demae-can menus, prices, fees, offers, and ratings by city or postal code. In addition, each dish stays linked to its restaurant ID.

Do you still cover Wolt and menu?

No, because both have left Japan. Wolt closed on March 4, 2026, and menu closed on September 30, 2026. Instead, we cover Rocket Now, the newest large app.

How do you handle consumption tax?

Every price is tax-inclusive, as Japanese law requires. Similarly, we tag each item with its likely rate, so 8% for food and 10% for alcohol.

Do you capture allergen information?

Yes. Whenever a menu lists allergens, we capture them for each dish. However, Japanese restaurants are not required to show them, so coverage varies.

Is the data legally sourced?

We collect only public listing data, such as menus, prices, ratings, and availability. In other words, we never collect personal or login-protected data. We also design the feed with Japan’s Act on the Protection of Personal Information in mind.

How do I get a free sample?

Just tell us the app, city, and fields you need. Then we send a free sample, usually as JSON or CSV.