Pricing

Rating

Developer

Actor stats

Categories

Share

Glovo Scraper

Pull structured data from any Glovo URL — restaurant menus, supermarket catalogs, shop listings, pharmacy lineups — in any of the 25+ countries Glovo operates in. Built for competitive price intelligence, grocery-retail market research, food-delivery analytics, and anyone who needs Glovo data at volume without babysitting a browser.

This is the only scraper on the Apify Store with full 360° supermarket coverage. Competitors stop at Glovo's featured-carousels landing page (~40 products per store). This one recursively walks Glovo's own content-node API and returns every SKU — verified: 1,299 products from SuperGlovo Madrid in 42 seconds.

What you can scrape

Paste any of these URL types into Start URLs — the scraper classifies each one and runs the right handler:

The same scraper works in every country Glovo operates — Spain, Portugal, Italy, France, Morocco, Georgia, Ukraine, Armenia, Bulgaria, Romania, Poland, Czech Republic, Serbia, Croatia, Bosnia, Kazakhstan, Kyrgyzstan, and more. Paste a URL with any language prefix (/en, /fr, /es, /pl...) and it routes correctly.

Optional enrichments

• storePage — on a /categories/<slug> URL, enqueue each store as a full PDP scrape so you get menu/catalog data in the same run
• shopCatalogDepth (default 2) — how deep to walk Glovo's category tree on supermarket + shop PDPs. 0 = featured carousels only (~40 products). 1–2 = expanded collections (~200–1,500 products — recommended default). 3–5 = exhaustive. Deeper = more HTTP calls = higher cost.
• menuItems — emit one flat dataset row per individual product (in addition to the nested per-store row). Useful for BI tools that prefer flat tables. Bills at $0.0001 per product.

Defaults are conservative. A run without enrichments stays on the commodity rate.

Why this scraper beats the alternative

Sample output — real record, trimmed

From glovoapp.com/en/es/madrid/stores/superglovo-mad with shopCatalogDepth: 2:

{
"type":"store-pdp",
"url":"https://glovoapp.com/en/es/madrid/stores/superglovo-mad",
"language":"en",
"country":"es",
"city":"madrid",
"slug":"superglovo-mad",
"layout":"TILE",
"storeId":"21033",
"addressId":"249456",
"store":{
"name":"El Súper de Glovo",
"rating":0.87,
"ratingCount":500,
"deliveryFee":"1,99 €",
"promoBadges":["-10% some items"],
"prime":true,
"minOrderInfo":"Reach 10,00 € to avoid an extra fee of 1,50 €",
"categoryType":"SUPERMARKET",
"isOpen":true
},
"products":[
{
"externalId":"LMC3AJ",
"storeProductId":"LMC3AJ",
"name":"Dr. Oetker Ristorante Piccola Pizza Margarita Airfryer 2u",
"price":3.95,
"originalPrice":7.90,
"currency":"EUR",
"imageUrl":"https://glovo.dhmedia.io/image/global-catalog-glovo/...",
"tags":[],
"promotion":{"type":"TWO_FOR_ONE","title":"2 for 1","promoId":"1333945124"},
"ean":"04001724038818",
"categoryId":"fab3f3df-83a7-4c39-b27f-37b48a4bd5c0",
"collectionGroupId":"52085513",
"collectionGroupName":"Mega Packs",
"sponsored":false,
"outOfStock":false
}
/* ...1,298 more products, same shape */
]
}

Restaurant PDPs emit the same top-level shape with layout: "ROW" and a nested menu.sections[] tree instead of a flat products[]. Category-page records emit one row per store card with type: "category-store-card".

Pricing

Per-event billing. You pay only for what you extract.

The shop pricing is deliberately split so you pay for the depth you actually walk. A shopCatalogDepth: 0 run (featured carousels only, no API calls) costs just $0.005 per shop. The default shopCatalogDepth: 2 unlocks the full catalog but bills only for the work Glovo's API actually does.

Real budgets:

Set a maxTotalChargeUsd cap on any run and the scraper stops cleanly once the budget lands. No surprise invoices.

Inputs

How it works

• No browser. The scraper parses Glovo's server-rendered HTML with Cheerio and calls Glovo's own content-node JSON API directly. Roughly 5–10× faster per store than browser-based scrapers on the Apify Store.
• Layout auto-detection. Every store PDP gets a layout probe against the HTML (ItemRow_* for restaurants, ItemTile_* for shops) and routes to the right extractor automatically. You never need to tell the scraper what kind of store you're scraping.
• Recursive catalog walk. On supermarket, grocery, shop, and pharmacy PDPs, the scraper reads storeId + addressId from Glovo's SSR hydration payload, seeds a BFS from the SSR products already on the page, then walks category deep-links via api.glovoapp.com/v4/stores/<id>/addresses/<id>/content/main?nodeType=DEEP_LINK&link=<slug> up to shopCatalogDepth levels. Products are deduped by externalId.
• CSS-module-proof selectors. Glovo's Next.js build rotates CSS module class hashes on every deploy (ItemRow_priceContainer__G5B13 → ItemRow_priceContainer__9pQr_). This scraper targets via class prefix ([class*="ItemRow_priceContainer"]), so redeploys don't break extraction.
• Resilient to rate-limiting. Each Crawlee session persists cookies through its lifetime. On HTTP 429 from the content API, the session retires and the work picks up on a fresh IP. You won't see failed requests in normal operation.

FAQ

Does the 360° catalog walk really cover every SKU? It walks every carousel and category deep-link the Glovo app's own navigation exposes on the store's landing, up to shopCatalogDepth levels. Depth 2 hit 1,299 unique SKUs on SuperGlovo Madrid during verification; depth 5 would go exhaustive. For a typical supermarket, depth 2 is ≥95% coverage.

Why is shopCatalogDepth capped at 5? Each deeper layer adds ~20 HTTP calls per store on average. Depth 5 on a Mercadona or Carrefour Hyper can fire hundreds of requests. The cap is a courtesy to Glovo's infrastructure and your budget. Depth 2 is the sweet spot — full coverage without runaway costs.

What countries does this work in? Every country Glovo operates in. URL parsing is country-agnostic: /en/ma/tanger/stores/..., /es/es/madrid/stores/..., /fr/fr/paris/stores/... — all work. The content-node API is regionalized via the glovo-location-country-code header, which the scraper sets from the URL automatically.

What's the difference between type: "category-store-card" and type: "store-pdp"? Category-card records come from parsing a /categories/<slug> listing page — they're lightweight (name, rating, delivery fee, promo badges) and map 1:1 to what's visible on Glovo's store-picker grid. Store-PDP records come from scraping a single store's page and contain either the full menu (restaurants) or full catalog (shops). When you set storePage: true, a category-URL run emits both types to the same dataset.

Does it work on free Apify plans? Yes. Glovo has no bot defense, so the default Apify datacenter proxy is sufficient. Free-tier accounts get $5 monthly credit — enough for ~1,000 full supermarket catalogs at depth 2, or ~16,000 restaurant menus.

How is the data kept fresh? Each run hits Glovo's live endpoints. No caching, no intermediate storage. A product listed five seconds before your run appears if Glovo's CDN has flushed.

Is this legal? Only public delivery-app data — no user accounts, no private orders, no seller-only dashboards. Same public surface Glovo's own web frontend serves anonymously without login.

What if Glovo changes their API? The scraper pins the current glovo-app-version string. If Glovo starts returning 403 on that version, we ship an updated pin. The /v4/stores/.../content/main endpoint schema has been stable through multiple Glovo frontend deploys.

How do I export the data? Dataset → Export in the Apify Console. CSV, JSON, JSONL, or XLSX with one click. Programmatically, fetch /v2/datasets/{id}/items to stream records, or push to BigQuery, Snowflake, or S3 via Apify's built-in integrations.

Can I run this on a schedule? Yes. Schedule the actor from the Apify Console (cron / hourly / daily). Combined with a maxTotalChargeUsd cap per run, you get predictable monthly spend with per-SKU granularity — useful for price-change alerting, out-of-stock monitoring, or promotion-calendar analytics.

Can I request a custom field? Yes. Open an issue via the Issues tab in the Apify Console. Simple field additions usually ship within a week.

Support

Open an issue via the Issues tab in the Apify Console, or message the actor owner directly.

Keywords

Glovo scraper, Glovo API, Glovo data export, food delivery data, grocery retail intelligence, supermarket catalog scraper, Glovo restaurants, Glovo menus, Glovo products, Glovo prices, competitive price intelligence, grocery SKU data, EAN barcode data, food delivery market research, Glovo Spain, Glovo Morocco, quick commerce data, last-mile delivery data, Glovo JSON export, Glovo categories, Glovo supermarkets.