Electronics Price Tracking API: Croma, Reliance Digital, vivo & OnePlus

Electronics prices in India move constantly: bank offers, festive sales, launch-week discounts and quiet MRP changes. If you run a deals site, a price tracker or a brand's channel monitoring, you need the live number from each store, not last week's crawl. QuickCommerce API now covers Reliance Digital, Croma, vivo & OnePlus for item lookups, bringing the total to 18 platforms on one key.

RelianceDigitalCromaVivoOnePlus

What you get per item

Finding item IDs

Every store uses its own product identifier. You only need to do this once per product; after that you poll by ID.

Look up one product

curl -H "X-API-Key: your-api-key" \
  "https://api.quickcommerceapi.com/v1/item?platform=Croma&item_id=317418&lat=12.9021&lon=77.6639&pincode=560102"

{
  "status": "success",
  "credits_remaining": 99,
  "data": {
    "item_id": "317418",
    "platform": "Croma",
    "count": 1,
    "items": [
      {
        "item_id": "317418",
        "name": "Apple iPhone 17 Pro (256GB, Deep Blue)",
        "available": true,
        "price": 126990,
        "mrp": 134900,
        "currency": "INR",
        "platform": "Croma",
        "deeplink": "https://www.croma.com/..."
      }
    ]
  }
}

Croma and Reliance Digital price and stock by pincode. Pass `pincode` if you know it; if you leave it out, the API derives it from `lat`/`lon`. The vivo and OnePlus stores have national pricing, so the location only satisfies the required parameters.

Batch up to 10 products per call

When you track a catalogue, use `/v1/items` with comma-separated IDs on one platform. It costs one credit per item, and every requested ID comes back in request order, with a `status: "failure"` entry if a product wasn't found, so a delisted SKU never breaks the batch.

curl -H "X-API-Key: your-api-key" \
  "https://api.quickcommerceapi.com/v1/items?platform=OnePlus&item_ids=P1120230:5011122818,P1120230&lat=12.9021&lon=77.6639"

A price-drop alert in Python

The tracker below keeps a watchlist per store, fetches it in batches, and flags any product whose price dropped since the last run or fell below your target. Run it from cron every few hours.

import json, os, pathlib, requests

API = "https://api.quickcommerceapi.com/v1/items"
HEADERS = {"X-API-Key": os.environ["QC_API_KEY"]}
LOC = {"lat": 12.9021, "lon": 77.6639, "pincode": "560102"}  # Bengaluru
STATE = pathlib.Path("last_prices.json")

# platform -> {item_id: target price in INR}
WATCHLIST = {
    "Croma": {"317418": 120000},
    "RelianceDigital": {"poco-m8x-5g-128-gb-4-gb-ram-smartphone-blue-mt782n-10555462": 18999},
    "OnePlus": {"P1120230:5011122818": 22999},
    "Vivo": {"10373:19585": 59999},
}

def fetch(platform, ids):
    for i in range(0, len(ids), 10):  # max 10 ids per call
        params = {**LOC, "platform": platform, "item_ids": ",".join(ids[i:i + 10])}
        r = requests.get(API, headers=HEADERS, params=params, timeout=60)
        r.raise_for_status()
        yield from r.json()["data"]["items"]

last = json.loads(STATE.read_text()) if STATE.exists() else {}
for platform, targets in WATCHLIST.items():
    for item in fetch(platform, list(targets)):
        if item.get("status") == "failure" or not item.get("price"):
            continue
        key = f"{platform}:{item['item_id']}"
        price, mrp = float(item["price"]), float(item.get("mrp") or 0)
        off = f" ({100 * (mrp - price) / mrp:.0f}% off MRP)" if mrp > price else ""
        if key in last and price < last[key]:
            print(f"DROP {platform} {item['name']}: {last[key]:.0f} -> {price:.0f}{off}")
        if price <= targets[item["item_id"]] and item.get("available"):
            print(f"TARGET HIT {platform} {item['name']} at {price:.0f}{off}")
        last[key] = price
STATE.write_text(json.dumps(last))

Swap the `print` calls for Slack, Telegram or email. For the grocery version of the same pattern, see automating price-drop alerts.

MRP vs offer price

Brand stores often list a high MRP and a much lower selling price, while retailers like Croma sit closer to MRP and compete through bank offers that aren't part of the listed price. Store both `price` and `mrp` on every poll: a falling `price` is a real discount, while a changed `mrp` with the same `price` is just a relabel. The discount you show users should come from `price`, never from MRP alone.

Who uses this

Try it

Open the API Playground, pick Croma, Reliance Digital, vivo or OnePlus with the `item` endpoint, and the sample item ID is filled in for you. New accounts get 100 free credits, enough for a full watchlist test.