Skip to content

Scrape Glovo Menus by Postal Code

Glovo store and menu pages are assembled by JavaScript and monitored by bot detection, so a plain HTTP fetch often returns a bare shell instead of the menu.

OUTPUT FORMATSHTMLJSONMarkdown

A managed scraping API addresses this by taking a Glovo URL, rendering the page in a headless browser, rotating residential proxies, and returning either the post-render HTML or structured JSON. The sections below cover the three common Glovo jobs, the request controls that matter for each, how credits are consumed, and a full plan reference table.

What you can collect from Glovo

A Glovo store page carries more than a menu. In one rendered response you can target menu items with their prices and modifiers, the store rating, the review count, the delivery-time estimate, the delivery fee and the operating hours. That makes the same request useful for three different jobs:

  • Delivery zone analysis. Collecting zone data supports market analysis and decisions about where service areas and operations should be optimised.
  • Menu benchmarking. Menu data lets you compare competitor offerings, pricing strategies and market trends.
  • Review analysis. Review data helps you read feedback patterns and adjust an offering or strategy accordingly.

Each job uses the same endpoint; what changes is which fields you extract and whether you need country-level routing.

Request controls and what each one does

The API exposes a small set of parameters that map directly onto Glovo's page behaviour. Use this as a field/control map:

  • render_js=true — runs the page in a real headless browser and returns the post-render HTML. Needed for any Glovo page whose menu or prices load client-side.
  • stealth_proxy — enable when a target gets aggressive; it adds a stronger proxy layer on top of the default residential rotation.
  • country_code — routes the request through a residential IP in that country. Use it when Glovo content varies by geography.
  • extract_rules — CSS selectors mapped to field names, returned as parsed JSON.
  • ai_extract_rules — a natural-language description of the fields you want, also returned as parsed JSON.

The default request already rotates residential proxies and uses a real headless browser, so ordinary traffic patterns are covered before you touch any of these flags.

A decision checklist before your first request

Work through these in order; each answer maps to a control above.

  1. Does the page need JavaScript? If the menu or prices are not in the raw HTML, set render_js=true. This is the most common cause of an empty-looking response.
  2. Does the content change by country? If yes, set country_code so the request exits from a residential IP in that market.
  3. Are you being blocked? If a target starts rejecting requests, turn on stealth_proxy rather than retrying harder.
  4. Do you need structured output? Choose extract_rules for stable CSS selectors, or ai_extract_rules when the field list is easier to describe in words.
  5. Are you hitting a per-target throttle? The API enforces concurrency limits per plan, not per-target rate limits — so space requests out or use multiple sessions if Glovo throttles aggressive patterns.
  6. Have you counted credits? See the worked example below before scaling up.

Worked credit example

Credits are consumed per successful request, and the cost depends on which features you enable. The supplied rules are:

  • A base request starts at 1 credit.
  • Each successful request that enables JS rendering costs 5 API credits.
  • Each successful request that enables Premium proxies costs 10 or 25 API credits, depending on whether JS rendering is disabled or not.

Read those rules as totals, not add-ons. A request with JS rendering on and premium proxies off costs 5 credits. A request with premium proxies on and JS rendering on costs 25 credits. A request with premium proxies on and JS rendering off costs 10 credits. If you are collecting 1,000 store pages a month with JS rendering only, that is 5,000 credits — well inside the Hobby plan's 75,000-credit allowance, but worth checking against your actual page count before you commit to a tier. Credits are valid for one month and do not roll over.

Blocked, throttled, or just not rendered?

These three failures look similar in a log but need different fixes:

  • Blocked. The response is a challenge page or an outright rejection. Fix: enable stealth_proxy. The default rotation already uses residential IPs and a real browser, so this is the escalation step.
  • Throttled. Requests succeed intermittently and fail in bursts. Fix: space them out or spread them across sessions; the API's limits are per-plan concurrency, not per-target rate limits.
  • Not rendered. The response is valid HTML but the menu or prices are missing. Fix: set render_js=true so the page executes server-side before the HTML is returned.

Checking which of the three you are seeing before changing parameters will save credits.

Getting from docs to first request

The workflow is four steps:

  1. Create an account to get an API key and the starting credit allowance.
  2. Install the SDK for your stack — Python, Node.js, Go, PHP, Ruby or Java — or use raw cURL.
  3. Send a Glovo URL to the endpoint with your API key; the service handles rendering and bot bypass and returns HTML or JSON.
  4. Add the advanced parameters only when the page needs them: render_js, stealth_proxy, country_code, extract_rules or ai_extract_rules.

There is also a dashboard request builder: paste a URL, set parameters, and copy the generated snippet in any of the supported languages. That covers the no-code path for a one-off request.

Plan and credit reference

The plan table below is a dated reference; prices and allowances can change, so confirm current terms before subscribing. All prices are exclusive of VAT. The table lists every standard and enterprise tier with its monthly price, API credit allowance, concurrency limit and feature inclusions. The Hobby tier starts at $19/mo with 75,000 credits and 25 concurrent requests; the largest listed enterprise tier is $5,799/mo with 120,000,000 credits and 900 concurrent requests. JavaScript rendering, rotating and premium proxies, geotargeting, and screenshots/extraction rules are included from the Hobby tier upward. Priority email support, a dedicated account manager and team management appear only from the Business tier.

Compliance and data handling

Compliance obligations depend on the operator and the jurisdiction, so treat this as a framework rather than a certification. A useful starting point is a policy that avoids collecting or storing personal data from scraped sites unless the user explicitly requests it. That distinction matters for review-collection jobs, where reviewer names or profiles may count as personal data under GDPR or CCPA. If your use case requires collecting those fields, establish your own legal basis before enabling extraction rules that target them.

Glovo scraper API plan comparison (dated reference)
PlanPrice /moAPI CreditsConcurrent requestsJS renderingRotating & Premium ProxiesGeotargetingScreenshots & Extraction RulesPriority Email SupportDedicated Account ManagerTeam Management
Hobby$1975,00025IncludedIncludedIncludedIncludedNot includedNot includedNot included
Freelance$49250,00050IncludedIncludedIncludedIncludedNot includedNot includedNot included
Startup (Recommended)$991,000,000100IncludedIncludedIncludedIncludedNot includedNot includedNot included
Business$2493,000,000200IncludedIncludedIncludedIncludedIncludedIncludedIncluded
Business +$5998,000,000400IncludedIncludedIncludedIncludedIncludedIncludedIncluded
Enterprise 14$99914,000,000500IncludedIncludedIncludedIncludedIncludedIncludedIncluded
Enterprise 24$1,59924,000,000600IncludedIncludedIncludedIncludedIncludedIncludedIncluded
Enterprise 41 (Recommended)$2,39941,000,000700IncludedIncludedIncludedIncludedIncludedIncludedIncluded
Enterprise 69$3,59969,000,000800IncludedIncludedIncludedIncludedIncludedIncludedIncluded
Enterprise 120$5,799120,000,000900IncludedIncludedIncludedIncludedIncludedIncludedIncluded

Dated reference captured from the publisher's page; prices and allowances can change. All prices exclusive of VAT. Credits valid for one month and do not roll over.

Frequently asked questions

Will I get blocked when scraping Glovo?

The service rotates residential proxies and uses a real headless browser, so requests resemble normal traffic. If a specific target becomes aggressive, enable stealth_proxy on the request to add a stronger proxy layer.

Can I scrape Glovo without writing code?

Yes. The dashboard request builder lets you paste a URL, set parameters, and copy a generated snippet in Python, Node, Go, PHP, Ruby or cURL. For one-off requests you never need to touch a code editor.

How do I handle JavaScript when scraping Glovo?

Set render_js=true. The page runs in a real headless browser, the JavaScript executes server-side, and you receive the post-render HTML.

Can I scrape Glovo from a specific country?

Yes. Pass country_code to route the request through a residential IP in that country. This is useful when Glovo content varies by geography.

What's the rate limit for scraping Glovo?

The API enforces concurrency limits per plan, not per-target rate limits. If Glovo throttles aggressive patterns, space out requests or use multiple sessions.

How do I get structured JSON from Glovo?

Pass extract_rules with CSS selectors mapped to field names, or use ai_extract_rules with a natural-language description of the fields you want. The response comes back as parsed JSON.