Local delivery coverage mapping
Mit Glovo-Endpunkten verwandelst du local delivery coverage mapping in wiederholbare API-Requests mit dokumentierten Inputs und JSON-Antworten.
Treat Glovo as a local marketplace: discover the supported city first, then follow that city's category, store, menu, and collection identifiers through the catalog.
Explore Glovo's country and city coverage, location-specific store categories, merchant listings, menus, and product prices as structured JSON.
Endpunkt-Familien
5
Dokumentierte Parameter
41
Beispiele
8
Live-Katalog-Snapshot
Aktive Endpunkte
8
Methoden
GET
Pflichtparameter
27
Schema-Referenzen
8
{
"platform": "Glovo",
"endpoint": "glovo-categories",
"method": "GET",
"path": "/glovo/categories",
"auth": "apiKey"
}Use Cases
Explore Glovo's country and city coverage, location-specific store categories, merchant listings, menus, and product prices as structured JSON.
Mit Glovo-Endpunkten verwandelst du local delivery coverage mapping in wiederholbare API-Requests mit dokumentierten Inputs und JSON-Antworten.
Mit Glovo-Endpunkten verwandelst du merchant and menu monitoring in wiederholbare API-Requests mit dokumentierten Inputs und JSON-Antworten.
Mit Glovo-Endpunkten verwandelst du city-level category and price research in wiederholbare API-Requests mit dokumentierten Inputs und JSON-Antworten.
Managed Execution
Jede Zahl unten stammt direkt aus dem Live-Glovo-Endpunktkatalog — 8 Endpunkte, 41 dokumentierte Request-Parameter und 8 veröffentlichte Response-Schemas — demselben Katalog, gegen den auch Docs und Playground laufen.
8 documented Glovo endpoints, grouped into 5 request families — Store, Stores and Categories, plus 2 more.
41 request parameters are documented across those Glovo endpoints, 27 of them required — the full input contract is public before you write any integration code.
8 of the 8 Glovo endpoints ship a recorded example response, and 8 carry a documented response schema — you can code against the real JSON before the first request.
Glovo endpoints document their error responses (400, 404 and 503) alongside the success schema, so a block, a rate limit, or a missing record comes back as a typed error rather than silently empty data.
8 hosted MCP tools back the Glovo endpoints, so an agent can call the same routes with the same parameters and the same JSON contract, with no custom glue.
Abdeckungskarte
/glovo/store
/glovo/stores/filters
/glovo/categories
/glovo/cities
/glovo/city
Endpunktkatalog
/glovo/citiesReturns Glovo's live directory of every country and city it delivers in, read from the directory its own landing page embeds. Each city carries the slug and the city code; every other Glovo endpoint takes country plus city (either the slug or the code) from here. The countries field always lists every supported country code, so the optional country filter's value space is discoverable; a country Glovo does not serve returns a 400 rather than an empty list. As of 2026-11-02 the directory covers 24 countries and 1,330 cities.
MCP-Tool glovo_cities
/glovo/cityReturns one city's market settings: its name, whether it is enabled, the languages it supports (the values the language parameter of every Glovo endpoint accepts for that city), its currency and its timezone. A city or country Glovo does not serve returns a 400 pointing to /glovo/cities.
MCP-Tool glovo_city
/glovo/categoriesReturns a city's top-level store categories (for example Food, Groceries, Shops, Pharmacy & Beauty). Each carries the id that /glovo/stores/filters and /glovo/stores take as category_id. Only categories of type STORES have a store list; other types, such as package delivery, are listed but have none. The set differs by city.
MCP-Tool glovo_categories
/glovo/stores/filtersReturns the cuisine or type filters (for example Burgers, Pizza, Healthy) that one category's store list accepts in one city. Each carries the id that /glovo/stores takes as filter_id. The filter set is category- and city-scoped, so call this for the same country, city and category_id you will pass to /glovo/stores. A category_id Glovo does not recognise in that city returns a 404.
MCP-Tool glovo_stores_filters
/glovo/storesReturns the first page of up to 50 stores from a city's category, in Glovo's own ranking, optionally narrowed to one cuisine or type filter. total_entries reports how many stores match in the city; only the first page is reachable without logging in (Glovo's server-rendered list ignores paging parameters), so use filter_id to reach other subsets. A category_id the city does not list, or a filter_id the category does not offer, returns a 404; a real category with no matching stores returns an empty list. The ranking and each store's distance are relative to the city's default point and can change between calls. Each store carries its id and address_id, which the store, menu and products endpoints take, plus its rating label, delivery estimate, delivery fee, promotions and open status.
MCP-Tool glovo_stores
/glovo/storeReturns one store's public detail: name, slug, category, address and coordinates, whether it is open and enabled, rating label and count, delivery and service fees, cuisine filters, promotions and its default address_id. An unknown store_id returns a 404.
MCP-Tool glovo_store
/glovo/store/menuReturns one store's menu as its tree of collections (for example Top sellers, Starters, Drinks). Each collection's slug is the value /glovo/store/products takes as collection. When address_id is omitted the store's own default location is looked up first, which costs one extra upstream call.
MCP-Tool glovo_store_menu
/glovo/store/productsReturns one store's products grouped into sections, each with a name, description, price, currency, display price, image URL, stock flag and its option groups (sizes, sides, toppings with price impact). Pass collection to return only one menu collection. limit caps the total products across sections (default 200, maximum 500); truncated reports whether more existed. When address_id is omitted the store's own default location is looked up first, which costs one extra upstream call.
MCP-Tool glovo_store_products
Verwandte APIs
Marketplaces & Retail
Separate an auction that is still open from a completed sale, and use BaT's own make and model directory to carry valid IDs into search and price-history requests.
Marketplaces & Retail
Use PetSmart's hierarchical paths to scope product searches, then keep product SKU, price range, online availability, pickup eligibility, and store inventory as separate fields.
Marketplaces & Retail
Research new, used, and vintage instruments across Reverb listings, seller shops, and the Price Guide. Keep current asking prices separate from historical sales, and preserve model, finish, year, condition, and currency when comparing gear.
So scrapst du Glovo
Glovo's official terms describe a marketplace where users buy from merchants and can request delivery or choose available pickup options; its SuperGlovo model covers a separate range of grocery and personal-care products. This is a local-commerce data surface, not an editorial publisher, and it has no author or byline route. The catalog is localized. On 2026-11-05, Madrid returned six top-level categories: Food, Groceries, Shops, Package Delivery, Pharmacy & Beauty, and El Súper de Glovo. Package Delivery was type SHIPMENT, while the other five exposed store-category behavior. The Food category reported 1,543 entries, but only the requested first-page store cards were returned.
Start with glovo-cities and choose a country plus city slug or code from its directory. Every other Glovo route requires both values. glovo-city returns market settings and supported languages; do not assume a city is available because a nearby market is.
glovo-categories returns IDs for one city. Only entries whose type is STORES can be passed into glovo-stores and glovo-stores-filters; shipment categories are listed for discovery but do not have store lists. The category set differs between cities.
glovo-stores returns at most 50 cards in Glovo's own ordering and reports total_entries. The Madrid Food sample returned 10 when limit=10 and showed merchant status, rating label, ETA, fee, promotion, and rank when available. The API does not expose arbitrary page offsets for this route.
Use a store id and address_id returned by glovo-stores for glovo-store, glovo-store-menu, and glovo-store-products. Menu collections return slugs for collection-filtered products. Keep country, city, and language with every record because availability, fees, and catalog content are local.
Open/enabled flags, delivery estimates, fees, and stock are observed market values that can change with location and time. The API reflects public catalog data; it does not submit orders, guarantee delivery, or expose a universal service area for every merchant.
FAQ
Resolve the city through glovo-cities, fetch that city's category IDs, then call glovo-stores with the chosen country, city, and category_id. A city code from the directory can also be used.
No. The categories endpoint can include non-store types such as SHIPMENT. Only categories marked STORES have a store list and filter set.
No. The documented store list is a single ranked page of up to 50 cards with total_entries. Treat it as the returned page rather than claiming offset pagination or a complete merchant archive.
No. They are location-specific live fields. Preserve the country, city, address, and capture time; the API is for public data collection, not an ordering or delivery guarantee.