Glovo store with its full menu

GET https://api.api.sh/glovo/v1/store
1 credit / call food & delivery try it in the playground →

One Glovo store: id, address id, slug, name, link, city code, type, open and enabled flags, rating, cuisines, delivery fee, service fee, Prime, scheduling, next opening time and closed message, the store's notices and the full menu: every section (top sellers, categories) with its products: id, name, description, price and price text, currency, out-of-stock and restricted flags, promotions, labels, dietary labels, image and option groups (min/max choices, each option's extra price).

Every response includes credits_used: the credits this call cost.

Parameters

nametypedescription
url string The store's glovoapp.com/<lang>/<country>/<city>/stores/<slug> link (from /glovo/v1/stores). Example: https://glovoapp.com/en/es/madrid/stores/vicio-madrid
country string With city and slug instead of url.
city string City slug (with country and slug).
slug string Store slug (with country and city).
language string Language of the texts: en (default), es, it, pt...

Every endpoint also takes fresh, raw, fields (see lean responses and caching).

Example

curl "https://api.api.sh/glovo/v1/store?url=https%3A%2F%2Fglovoapp.com%2Fen%2Fes%2Fmadrid%2Fstores%2Fvicio-madrid" \
  -H "x-api-key: $APISH_KEY"

Response

A JSON object with the fields described above, plus raw (the source's own data), cached, fetched_at and credits_used. Errors return {"success": false, "error": "…"} with the HTTP status (see errors). A lookup that ran but found nothing (404) costs the price above; refused calls and errors on our side are free (what's charged).

The fastest way to see the full response is the playground: it runs this endpoint with your account and shows the exact JSON.