foodpanda Home Feed Scraper

foodpanda Home Feed Scraper pulls foodpanda's real home-screen feed — cuisine-category swimlanes, campaigns, and a rich per-vendor shape (live availability status, rating, chain, delivery-time estimation) — for one or more locations across 11 Asian markets. No foodpanda account, app, or scraping infrastructure required.

Spun off from the mature foodpanda All-in-One API for teams that want a run-and-export dataset of home-feed data rather than a live standby API.

Why use this Actor?

• Market research — see what foodpanda itself surfaces as top cuisines/restaurants for a given location.
• Campaign monitoring — track which promotional campaigns foodpanda is running in a market.
• Availability tracking — the home feed's per-vendor shape includes live availability status and delivery-time estimates not present in the plain restaurant listing.

How it was found

This endpoint (GetVendorListPage) is invoked by the web app via Apollo's Automatic Persisted Queries — identified by a sha256 hash of the query text rather than the text itself. Once the server has cached that hash from real web traffic, any caller can replay it by hash alone, forever — confirmed live via plain curl, no browser or query text needed post-capture.

Pagination

Fully paginated — confirmed live via the response's own tokenPagination.token field (found via the schema-validation-error technique: a deliberately-unknown input field echoes back the real VendorListingPageInput SDL, which includes tokenPagination: TokenPaginationInput). The Actor automatically chains pages until the server stops returning a token, or maxItemsPerLocation is reached — verified live that 2 real chained pages return zero overlapping vendor codes.

Input

Field	Required	Description
locations	yes	Array of { country, lat, lng } objects — one or more locations to fetch the home feed for. country is one of bd, hk, kh, la, mm, my, ph, pk, sg, th, tw.
maxItemsPerLocation	no	Stop once this many components have been pushed for a given location. Leave empty to fetch every page (can be hundreds of components for a dense area).

Output

One dataset row per feed component (cuisine swimlane, vendor card, etc.):

{
    "country": "bd",
    "lat": 23.803782,
    "lng": 90.414964,
    "__typename": "SwimlaneComponent",
    "headline": "Cuisines",
    "entities": [{ "__typename": "Cuisine", "id": "86", "name": "Fast Food" }]
}

Pricing / Cost estimation

Billed pay-per-event — one home-feed-component event per component scraped, plus a flat apify-actor-start event per run.

FAQ, disclaimers, and support

This is an unofficial Actor, not affiliated with or endorsed by foodpanda or Delivery Hero SE. It calls foodpanda's own public GraphQL API ({country}.fd-api.com/graphql), the same one the real web app uses for a signed-out user — no account credentials or bypassed authentication involved.

Found an issue or need a custom field added? Use the Issues tab on this Actor's page.