Bigbasket Keyword Rank Tracker

Captures the full BigBasket search results slate for a keyword in a specific Indian location, with every product's rank, the ad slots marked and the ad id holding each one. Availability is store level, so each pincode resolves to the store serving that area and the ranks match what a local shopper sees.

What you get

• One row per search result position: position, product_id, name, brand, price, mrp and in_stock.
• is_sponsored on paid slots, read from BigBasket's own ad markers, with ad_campaign_id carrying the ad id.
• Full location context on every row: location_label, pincode and store_id, which on BigBasket names the serving area.
• captured_at on every row, so a time series is built by appending runs.
• Ranks for the whole slate, not just one brand, so competitor rank and ad share stay derivable.
• No browser anywhere in the path, which makes this the fastest of the quick-commerce rank trackers.

Input

Give the keywords and at least one Indian pincode.

{
  "keywords": ["atta"],
  "locations": [
    {
      "label": "Bengaluru-MGRoad",
      "lat": 12.9716,
      "lon": 77.5946,
      "pincode": "560001"
    }
  ],
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": ["RESIDENTIAL"],
    "apifyProxyCountry": "IN"
  },
  "pages": 1
}

• keywords (required): search terms to rank. Duplicates are ignored.
• pincodes: Indian 6-digit pincodes, for example ["560001"]. Each is resolved to coordinates and BigBasket picks the store serving that point.
• locations (advanced): exact store targets as {"label","lat","lon","pincode"}.
• pages: result pages to walk per keyword. BigBasket serves 40 products a page, and the actor stops once the reported total is reached.
• proxyConfiguration: egress for the run. An Indian residential proxy is the default and is recommended.

Output

One dataset row per search result position, per keyword and location.

{
  "captured_at": "2026-09-11T09:02:16+00:00",
  "platform": "bigbasket",
  "keyword": "atta",
  "location_label": "Bengaluru-MGRoad",
  "pincode": "560001",
  "store_id": "KG Halli, Ashok Nagar",
  "position": 1,
  "is_sponsored": true,
  "ad_campaign_id": "afad79fb4e76acb31db8e42c879a9572",
  "product_id": "126903",
  "name": "Aashirvaad Atta/Godihittu - Whole Wheat 5 kg",
  "brand": "Aashirvaad",
  "price": 306,
  "mrp": 358,
  "in_stock": true,
  "inventory": null
}

A live run of one keyword in Bengaluru returned 20 rows, 1 of them sponsored. inventory is always null: BigBasket does not publish unit counts. ad_campaign_id is null on organic rows.

Use cases

• Keyword rank tracking for your own SKUs, city by city, from keyword, position and location_label.
• Ad-slot share: how many of the top positions carry is_sponsored true, and which ad ids hold them.
• Competitor share of search, counting brand across the whole ranked slate.
• Price and MRP monitoring at rank, and assortment differences between two pincodes in one run.

Notes and limits

• 40 products a page. Raise pages to walk deeper into a keyword's slate.
• The location binds the serving store and also unlocks BigBasket's ad slots. Without one, the default service area serves no ads at all and every result looks organic, so always pass a pincode.
• A point with no serving store fails that capture with a clear unserved message rather than logging the default area's ranks.
• Some stores answer no results for any term. That is reported per location as a failed capture, not as a silent zero.
• An Indian residential proxy is the default and is recommended.
• inventory is always null on this platform.
• India only.

FAQ

Do I need a proxy? An Indian residential proxy is recommended and is the default.

How many results can I get? 40 positions a page per keyword and location, up to pages of them or until BigBasket's reported total is reached.

Does it need a login or an API key? No.

How does a pincode pick a store? The pincode is resolved to coordinates and those coordinates are bound to the session before searching, which selects the dark store and enables the ad slots. The serving area comes back in store_id.

Why do some captures return zero rows? Either the keyword has no matches at that store, or the store itself answers nothing. Both are logged per keyword and location with the store name, so the two cases stay distinguishable.