subimpact WhatsApp us

foodora Reviews API

foodora Reviews API returns one JSON row per public foodora review: reviewText, ratingOverall, ratingFood, ratingRider, reviewerName, likes, vendorReply, createdAt and reviewUrl, in Norwegian, Hungarian or Czech exactly as written, plus restaurant context in discovery mode. It covers Norway, Hungary and Czechia and costs $0.0015 per review ($1.50 per 1,000), falling to $1.20 per 1,000 on Gold and above.

from $0.0015 per review, $1.50 per 1,000, down to $0.0012 on higher Apify plans · Updated Nov 2026, version 0.1.3

Key facts

Price
from $0.0015 per review, $1.50 per 1,000, down to $0.0012 on higher Apify plans
Pricing model
Pay per event
Output
JSON, CSV, Excel, XML, RSS via Apify datasets
Access
Apify Console, REST API, Python and JS clients
Version
Updated Nov 2026, version 0.1.3
Usage
100.0% successful runs (30 days)
Actor
subimpact/foodora-reviews-api

Who it is for

  • Restaurant chains monitoring sentiment across Nordic and Central European cities
  • Delivery operations teams reading rider complaints by branch
  • Market researchers comparing foodora cities such as Oslo and Prague
  • NLP teams assembling Norwegian, Hungarian and Czech review corpora

Use cases

Compare three markets in one run

Paste restaurant URLs from different countries into vendorUrls, for example a foodora.no and a foodora.cz page, and the market is read from each URL rather than from one country input. Every row carries its country code, so a chain operating in Oslo, Budapest and Prague can chart ratingOverall per market from a single dataset instead of three runs.

Find rider complaints

ratingRider is scored separately from ratingFood where foodora publishes it, and the ratings array lists every topic. Filter to rows with a low rider score and a high food score, then group by vendorCode: that separates a delivery problem from a kitchen problem, which is the difference between changing a courier partner and changing a menu.

Discover a city's restaurants

Set locations to Oslo, Bergen, Trondheim, Budapest, Debrecen, Prague or Brno, or a lat,lng pair such as 59.9139,10.7522, and choose maxRestaurantsPerLocation. Each row then fills restaurantName, restaurantRating, restaurantReviewCount, restaurantCuisines and coordinates. Discovery is free, so the charge is only for the reviews that follow.

Audit who replies to reviews

vendorReply holds the public reply where one exists and null where it does not. Comparing reply share against rating band per vendorCode shows who answers criticism, and exporting reviewText with vendorReply gives paired examples of good and weak recovery wording. That is useful training material for a support team or a drafted reply model.

Build a local-language corpus

Reviews arrive in the language the customer wrote, so a Prague run returns Czech text and an Oslo run Norwegian, each with per-topic scores and a date. Set maxTotalReviews to your budget and minRestaurantReviews to skip near-empty outlets, then use ratingOverall and createdAt as labels. Info and error rows carry no review and are never charged.

Output fields

FieldTypeDescription
rowType string/null review for a review, info/error for a location note (never charged)
platform string/null foodora
country string/null Market code: no, hu or cz
vendorCode string/null Restaurant code
location string/null Discovery location this restaurant came from (null when you passed codes)
reviewId string/null Unique review UUID
reviewText string/null Full review text
reviewerName string/null Display name of reviewer (or 'Anonymous')
reviewerId string/null Reviewer identifier
isAnonymous boolean/null Whether the reviewer chose to stay anonymous
ratingOverall integer/null Overall star rating (1-5)
ratingFood integer/null Food score (1-5) when present
Show all 25 fields
FieldTypeDescription
ratingRider integer/null Rider score (1-5) when present
ratings array/null Full per-topic ratings array
likes integer/null Helpful/like count
vendorReply string/null Vendor reply text when present
createdAt string/null Review creation timestamp (ISO)
reviewUrl string/null Public review page URL
restaurantName string/null Restaurant name from the listing (null when you passed codes)
restaurantRating number/null Restaurant average rating from the listing, e.g. 4.5
restaurantReviewCount integer/null How many reviews the restaurant has in total, from the listing
restaurantCuisines array/null Cuisine names from the listing
restaurantLatitude number/null Restaurant latitude from the listing
restaurantLongitude number/null Restaurant longitude from the listing
error string/null Message on info/error rows (a location that could not be used); null on review rows

Sample output

From one of our own test runs on 20 Nov 2026, trimmed. Personal data is redacted.

2 rows, first 3 shown

[
  {
    "rowType": "review",
    "platform": "foodora",
    "vendorCode": "n5fy",
    "country": "no",
    "reviewId": "87121aba-8972-5083-afcb-f89caa1fc755",
    "reviewText": "bestillte chicken burger, men fikk en annen type burger. smakte som papp.  føler meg lurt.",
    "reviewerName": "Magenis",
    "reviewerId": "nol17df5",
    "isAnonymous": false,
    "ratingOverall": 1,
    "ratingFood": 1,
    "ratingRider": null,
    "ratings": [
      {
        "topic": "overall",
        "score": 1
      },
      {
        "topic": "restaurant_food",
        "score": 1
      }
    ],
    "likes": 0,
    "vendorReply": null,
    "createdAt": "2026-11-18T19:04:38Z",
    "reviewUrl": "https://www.foodora.no/restaurant/n5fy/reviews",
    "restaurantName": null,
    "restaurantRating": null,
    "restaurantReviewCount": null,
    "restaurantCuisines": null,
    "restaurantLatitude": null,
    "restaurantLongitude": null,
    "location": null,
    "error": null
  },
  {
    "rowType": "review",
    "platform": "foodora",
    "vendorCode": "n5fy",
    "country": "no",
    "reviewId": "643da5ac-4d4e-5ba5-abff-9ff35b48e983",
    "reviewText": "Beste burger i Norge 😍",
    "reviewerName": "Mohammad",
    "reviewerId": "no4drelg",
    "isAnonymous": false,
    "ratingOverall": 5,
    "ratingFood": 5,
    "ratingRider": 1,
    "ratings": [
      {
        "topic": "overall",
        "score": 5
      },
      {
        "topic": "restaurant_food",
        "score": 5
      },
      {
        "topic": "rider",
        "score": 1
      }
    ],
    "likes": 0,
    "vendorReply": null,
    "createdAt": "2026-11-18T13:53:08Z",
    "reviewUrl": "https://www.foodora.no/restaurant/n5fy/reviews",
    "restaurantName": null,
    "restaurantRating": null,
    "restaurantReviewCount": null,
    "restaurantCuisines": null,
    "restaurantLatitude": null,
    "restaurantLongitude": null,
    "location": null,
    "error": null
  }
]

Input

FieldTypeRequiredDescriptionDefault
vendorCodes array No One or more foodora restaurant codes (e.g. n5fy). The code is the short segment in a restaurant URL: https://www.foodora.no/restaurant//. You can also paste full restaurant URLs, codes are extracted automatically. Leave empty to use `loc... -
vendorUrls array No Alternative to restaurant codes: paste full foodora restaurant URLs, for example https://www.foodora.no/restaurant/n5fy/troys-burger-grunerlokka. Codes and the market are read from the URL, so `country` can be left out. -
locations array No Find restaurants near a place instead of pasting codes. Each entry is a city preset name (Oslo, Bergen, Trondheim, Budapest, Debrecen, Prague, Brno) or a "lat,lng" pair such as 59.9139,10.7522. Restaurants come back in the platform's own... -
maxRestaurantsPerLocation integer No How many restaurants to take from the listing for each location (1-500). Only used in discovery mode. 20
minRestaurantReviews integer No Skip restaurants that have fewer reviews than this in the listing (0 = keep all). Useful to avoid tiny/new restaurants with nothing to scrape. 0
country string No foodora market. Norway (no) is the default; Hungary (hu) and Czechia (cz) run on the same reviews backend. no
maxReviewsPerVendor integer No Maximum number of reviews to fetch per restaurant. 0 = all available (paginate until exhausted). 0
maxVendors integer No Maximum number of restaurants to process after discovery or from your code list. 0 = all. 0
maxTotalReviews integer No Safety cap on the total number of reviews delivered across ALL restaurants in the run, protecting against unexpected bill size on wide inputs. Lower it or raise it freely; 0 = unlimited. 100

Example input

{
  "vendorCodes": [
    "n5fy"
  ],
  "locations": [
    "Oslo"
  ],
  "country": "no",
  "maxTotalReviews": 100
}

Pricing

EventWhat it meansPriceLowest tier
review One foodora review delivered to the dataset (text, ratings, reviewer, reply, restaurant context where known). Platform usage included. $0.0015 $0.0012

$1.50 at the listed price, or $1.20 on higher Apify plans, for 1,000 reviews.

Prices from the Apify Store on 20 November 2026. Apify shows the final price before each run.

How it compares with other Apify actors

Price per 1,000 reviews at Apify Store list prices. Every row is a live listing on the Store, read on 20 Nov 2026, so a buyer can check each number at the source.

Actor Price per 1,000 reviews (Free plan) Higher plans (Gold) Start fee per run Platform usage Users Rating Last build
foodora Reviews Scraper — Ratings, Comments & Replies This API Pay per event $1.50 $1.20 None Included 1 No reviews yet 18 Nov 2026
Foodpanda & Foodora Restaurants Scraper Direct match, pay per event $1.39 $1.09 $0.01 Included 2 No reviews yet 3 Nov 2026
Foodora Scraper | Restaurants, Menus, Reviews & Offers Partial match, pay per event Charges per delivered row, whatever its type, plus an Actor start fee. $0.005 Included 12 No reviews yet 19 Nov 2026
Foodora Scraper — Restaurants, Menus & Prices Partial match, pay per event Charges per vendor scraped, plus an Actor start charge, and returns no review text. $0.00005 Included 5 No reviews yet 8 Nov 2026
Food Delivery Scraper Partial match, pay per event $2.00 $0.7 $0.0001 Included 65 5.0 (3 reviews) 11 Nov 2026
Where Foodpanda & Foodora Restaurants Scraper is stronger

Where Foodpanda & Foodora Restaurants Scraper is stronger

  • Also covers foodpanda, with phone, legal name and trade register number
  • Menu, opening hours and offers can be pulled on demand
  • Can search by chain, cuisine or a whole country

Where this API is stronger

  • Review rows separate food and rider ratings as well as overall
  • The actor is review focused, so no restaurant or menu rows to filter out
  • Vendor replies and review likes are part of each row
Where Foodora Scraper | Restaurants, Menus, Reviews & Offers is stronger

Where Foodora Scraper | Restaurants, Menus, Reviews & Offers is stronger

  • Covers menus, offers and several row types inside one actor
  • Runs across five European foodora markets
  • Output carries row type and item type fields for easy filtering

Where this API is stronger

  • One row per review with text, per topic ratings and vendor replies
  • Charges apply to reviews rather than to whole restaurants
  • Restaurant rating, cuisines and coordinates travel with each review
Where Foodora Scraper — Restaurants, Menus & Prices is stronger

Where Foodora Scraper — Restaurants, Menus & Prices is stronger

  • Returns menu item prices and delivery fees for each restaurant
  • Can sweep a whole city using an optional geo grid
  • Returns open status and minimum order with each vendor

Where this API is stronger

  • Returns review text and per topic ratings, which their rows do not carry
  • Accepts vendor codes and vendor URLs as well as cities
  • Review rows include likes and vendor replies
Where Food Delivery Scraper is stronger

Where Food Delivery Scraper is stronger

  • Covers many delivery platforms well beyond foodora
  • Can return menus and restaurant listings in the same run
  • Separate events let one job mix listings, menus and reviews

Where this API is stronger

  • Focused on foodora reviews, with food, rider and overall ratings
  • Vendor replies and likes are captured with each review
  • Plain HTTP, so no browser rendering charge per item

Foodora review data is available from a mixed use actor, two restaurant and menu scrapers, and one dedicated review event in a multi platform tool. Buyers who need menus, offers or restaurant records have better fits above. Teams that mainly need review text with per topic ratings, vendor replies and restaurant context get the leanest path here.

Prices are Apify Store list prices, checked 20 Nov 2026. Platform usage 'Paid separately' means Apify bills compute on top of the event price. Check each listing before you buy.

How to run it

  1. Open a restaurant on foodora; the URL looks like https://www.foodora.no/restaurant/n5fy/troys-burger-grunerlokka.
  2. Paste the four character code n5fy into vendorCodes, or paste the whole URL into vendorUrls so codes and markets are read for you.
  3. Or set locations to Oslo, Budapest or Prague with maxRestaurantsPerLocation to find restaurants first.
  4. Set maxReviewsPerVendor, for example 100, and maxTotalReviews as the run's ceiling, 100 by default.
  5. Start the run in the Apify Console and open the dataset; one row per review appears with its ratings and reply.
  6. Export as JSON, CSV or Excel, or read the dataset through the Apify API.

cURL

curl -X POST "https://api.apify.com/v2/acts/subimpact~foodora-reviews-api/run-sync-get-dataset-items?token=$APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"vendorCodes":["n5fy"],"locations":["Oslo"],"country":"no","maxTotalReviews":100}'

Python

from apify_client import ApifyClient

client = ApifyClient("<YOUR_APIFY_TOKEN>")
run = client.actor("subimpact/foodora-reviews-api").call(run_input={"vendorCodes":["n5fy"],"locations":["Oslo"],"country":"no","maxTotalReviews":100})

for item in client.dataset(run["default_dataset_id"]).iterate_items():
    print(item)

JavaScript

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: '<YOUR_APIFY_TOKEN>' });
const run = await client.actor('subimpact/foodora-reviews-api').call({"vendorCodes":["n5fy"],"locations":["Oslo"],"country":"no","maxTotalReviews":100});
const { items } = await client.dataset(run.defaultDatasetId).listItems();

console.log(items);

n8n

Use the Apify node (Run an Actor).
Actor ID: subimpact/foodora-reviews-api
Input JSON: paste the example input above.

Limits

  • Only three markets are covered: Norway, Hungary and Czechia.
  • Older review pages depend on the platform's paging cursor, so a large per-restaurant cap may deliver fewer rows.
  • Reviews vary by restaurant, and an empty result is normal for new or small outlets.
  • Restaurant context fields are only filled in discovery mode; a code or URL input leaves them null.

Questions people ask

What does one foodora review cost?

$0.0015 per review, which is $1.50 per 1,000 reviews on the Free plan, dropping to $1.20 per 1,000 on Gold and above. You pay only for reviews delivered, compute is included in the event price, and discovery rows plus info and error rows are free.

Which foodora markets are supported?

Norway, Hungary and Czechia, with the country input set to no, hu or cz. When you paste full restaurant URLs you can leave country out, because the market is read from each link, which is how a mixed three-market run works.

Is a foodora account needed?

No. The Actor reads foodora's public review surface over plain HTTP with no browser, no account and no checkout access. Reviewer names appear as foodora shows them, including Anonymous where the platform hides the name.

Why can a restaurant return fewer rows than the cap?

A reviews page holds up to 30 reviews, and older pages depend on the platform's paging cursor. When the cursor stops moving forward the Actor ends that restaurant instead of repeating rows, so a large maxReviewsPerVendor can legitimately deliver less. New or small restaurants can return nothing.

What is the difference between codes and URLs?

A code such as n5fy is the short segment in a foodora restaurant URL and works within its own market. A full URL carries the market as well, so it is the safer input when your list spans Norway, Hungary and Czechia in one run.

Are reviews in the local language?

Yes. reviewText is the customer's own wording with no translation, and the ratings array carries the per-topic scores beside it. That makes the dataset usable as Norwegian, Hungarian or Czech training data as well as for per-market reporting.

Can I schedule weekly monitoring?

Yes. Apify schedules rerun the same input, and reviewId is a stable UUID plus createdAt is on every row, so consecutive snapshots can be diffed. Keep maxTotalReviews modest for a recurring job and raise it when a branch starts collecting feedback quickly.

Need a data source that is not here?

We build and run scrapers for sites that have no public API. Tell us the site, the fields and how often you need them.