Glovo answers a datacenter client with HTTP 202 and an empty page, which is the same trap Swiggy sets and the first thing to know about scraping it: a 202 with no body is not success, it is AWS WAF's challenge action handing back a JavaScript interstitial that a real browser solves and a script never does. On 24 August 2026 our datacenter server got exactly that, and so did the three free proxies that managed to connect. Behind the challenge is a delivery and quick-commerce platform with unusual reach: founded in Barcelona in 2015, part of Delivery Hero since 2022, Glovo runs in 23 markets and 1,800 cities across Europe, Africa and Central Asia, and its quick-commerce arm alone generates over a billion euros in sales for partners (Glovo, 14 May 2025).
Glovo's edge is where it operates: it ranks first in markets bigger platforms skip, such as Morocco, Kenya, Romania and Georgia, which makes its price and coverage data hard to get anywhere else. Every storefront is built per city and per address, so reading a market is reading many addresses on a schedule, through a challenge that scores the client. This page covers the door, the jobs, the type, setup, sizing and limits.
Which proxy fits
Residential proxies pinned to the country, and where possible the city, of the storefront you read, driving a real browser, one session per address. A static ISP proxy per account for any courier or partner login. Datacenter and free exits get the 202 and nothing else; the count is below.
Glovo as a target
Restaurant storefronts, built per address, with restaurant-set prices and Glovo-set fees. Dark-store groceries and retail, Glovo's fastest-growing business, priced per store, which makes it a quick-commerce price target. And 23 national markets, each in its own language and currency, several of them places where no rival publishes comparable data.
Behind AWS WAF, glovoapp.com is a JavaScript application. Once the challenge is solved, storefronts and the dark-store catalog load through Glovo's own API calls keyed to the address in the session.
Jobs a proxy is right for
- Menu and price monitoring across markets. Chains audit their own listings and franchisee markups; analysts compare delivery pricing between, say, Casablanca and Bucharest in local currency.
- Dark-store and quick-commerce pricing. Glovo's own grocery and retail prices per city, against local supermarkets and other quick-commerce players, in markets where this is the only readable source.
- Coverage by address. Which restaurants and stores reach an address, discovered by entering it, for site selection and competitor mapping.
- Fee and Prime research. Delivery fees, service fees and membership perks per country, and how they move.
- Emerging-market intelligence. Glovo's strength in Africa and Central Asia makes it the primary window into delivery pricing in markets that global datasets miss, read from an exit in each country, the method in geo-testing with proxies.
Jobs a proxy is not for
Courier accounts. Identity and right-to-work checks in each country.
Promotion credits and multiple accounts. Accounts attach to a local phone, payment method and device; farming credits runs against Glovo's terms.
Ordering from abroad. A local payment method and a real address in the delivery area are not network properties.
The door: HTTP 202 and an empty page
On 24 August 2026 a single request to glovoapp.com from a datacenter server in Germany, with a normal browser user-agent, returned HTTP 202 with no title and no content, served through CloudFront. Of twenty elite HTTP proxies from our free proxy list, one request apiece, 17 never connected, three connected to the same empty 202, and none loaded the site.
The 202 is the whole hazard. It reads as "accepted", and a scraper that treats it as success records empty pages all night; here it means the request was accepted into a challenge that a real browser has to finish. Getting past AWS WAF explains the interstitial and the token it sets. The answer is the same as for any JavaScript challenge: a real browser on an address the challenge is served to rarely, which is a residential address in the target country.
Type by job
| Glovo job | Proxy type | Why |
|---|---|---|
| Menu and price monitoring across markets | Rotating residential, country and city pinned, session per address | Solves the challenge with a real browser; reads as a local |
| Dark-store and quick-commerce pricing | Rotating residential, city-pinned | Prices are per store, chosen by address |
| Coverage by address | Rotating residential, session per address | Each address is one session |
| Emerging-market intelligence | Residential in the target country | The market is the exit |
| Courier or partner login | ISP (static residential) | One fixed, trusted location per account |
| Anything | Datacenter or free | Challenged at the door, 0 of 3 |
For the general split, datacenter vs residential proxies.
Free proxies here
Zero of three, and the free pool is thinnest in exactly the markets Glovo is strongest in, so even a manual look at a Casablanca or Tbilisi storefront is a matter of luck. Filter our free proxy list to the country and verify in the proxy checker if you want to try one. For a real read, our residential proxies start at $0.44/GB, pay as you go, no KYC, pinned to any Glovo market we cover.
Setup
- Country-pinned residential exit, real browser, always. There is no fetch-only route through a JavaScript challenge, and the country selects the market. Launch flags are in the Playwright proxy guide.
- Check the status code and the body. Treat any 202 with an empty body as "not loaded" and let the browser finish; never record it as data.
- One session per address, currency recorded. Twenty-three markets means many currencies; store it with every price. Sticky vs rotating proxy sessions covers the two modes.
- Pace for the market's pool size. Small-market pools are smaller, so their exits get reused more; slow down there. Avoiding IP bans while scraping has the rest.
Sizing
Auditing a chain across 6 Glovo markets, weekly:
markets 6
cities per market 2-4
addresses per city 8
sessions per exit per day 3-5
exits per market ~8-12 residential, city-pinned
Residential meters bandwidth; storefront and catalog pages with images blocked are small, so the address list sets the bill. Pricing is pay as you go with no expiring balance.
The boundary
A residential address in the target country is what turns the 202 into a page, with a real browser solving the challenge; the proxy does nothing for courier identity, account links, local payment or Glovo's terms, which prohibit scraping. Inside them, a country-pinned residential exit lets a legitimate data job read public storefronts and dark-store catalogs across 23 markets the way locals in each city see them: one address per session, human pacing, the challenge rate logged.
The Indian platform with the same 202 challenge is in proxies for Swiggy; the German rival with a Cloudflare challenge is in proxies for Lieferando.
Sources
- Glovo, 14 May 2025, Glovo celebrates 10 years (founded 2015 in Barcelona; part of Delivery Hero since 2022; 23 markets and 1,800 cities across Europe, Africa and Central Asia; quick commerce over one billion euros in partner sales): about.glovoapp.com
- HProxy measurement, 24 August 2026: one direct request from a datacenter server (HTTP 202, empty body, CloudFront) and 20 elite HTTP proxies from our free proxy list (17 no connection, 3 challenge, 0 site).