Skip to documentation
Browse documentation

Multi-location search

Run one Zepto product query across up to ten delivery locations and return local result groups for comparison.

Capability ID zepto.search.multi_location
Maximum runtime 180 seconds
View raw

POST /execute Shared execution endpoint

Input parameters

Provide query and locations. locations accepts 1 to 10 objects; each object contains either a six-digit pincode or both latitude and longitude.

limit accepts 1 to 100 products per local search and max_pages accepts 1 to 20 product pages.

limit integer optional

Maximum number of results to return. From 1 to 100. Default: `20`.

Example 2
locations array<object> required
Example [{"pincode":"560067"},{"latitude":12.9716,"longitude":77.5946}]
locations[].latitude number optional

Latitude in decimal degrees. From -90 to 90.

locations[].longitude number optional

Longitude in decimal degrees. From -180 to 180.

locations[].pincode string optional

Six-digit Indian pincode. When provided, Upscrape resolves coordinates and the Zepto delivery store automatically.

max_pages integer optional

Maximum number of result pages to fetch. From 1 to 20. Default: `10`.

Example 1
query string required

Search query.

Example rice

Response

Successful output is returned in results[0].data.

Results are grouped by requested location. Keep each group’s location attribution and treat product rows at different stores as separate observations rather than a deduplicated national SKU record.

Apply the same bounded-search interpretation as zepto.search: returned rows and limits do not prove exhaustive inventory.

Illustrative sample The example response is shown in the response panel.

Illustrative output fields

Values illustrate one response. Read the guidance above for missing values and limits; fields can vary with the requested operation and the data available.

PathObserved typeExample
captured_at string 2026-09-24T09:56:09.12695688Z
query string rice
results array 2 items
results array 2 items

Execution behavior

A 200 response completed inline. A 202 response was queued; poll GET /jobs/:id until the job reaches completed or failed.

Overview, pricing and sample data for every endpoint: Zepto API