Tesco Grocery Data Scraper API
Tesco product pages are rendered with JavaScript and protected by bot detection, so a plain HTTP fetch often returns incomplete or blocked HTML.
This page explains how a managed scraping API handles that layer for you and what a Tesco product request can return: price and unit price, product description and allergens, and customer ratings. It is written for teams building UK grocery pricing, product-quality or review datasets who want to know which fields are available and which request options affect cost.
What a Tesco request returns
A single request takes a Tesco URL and returns the rendered page, or structured JSON if you supply extraction rules. The fields commonly targeted on a Tesco product page are product name, price, unit price, brand, category, Clubcard pricing, allergen information, ingredient list and customer ratings. Review counts and review text are also available for review-mining workflows.
That makes the same endpoint usable for three different jobs: price and unit-price tracking across SKUs, product-description collection for clean-label and compliance datasets, and rating and review collection for product-quality analysis. The field list is the same regardless of which job you are doing; what changes is the extraction rule you attach and how often you re-request the page.
Field and control map
Use this map to decide which request options you actually need. It is a planning aid, not a promise that every field appears on every product page.
- Price and unit price: returned in the rendered HTML; target with extract_rules or describe in ai_extract_rules.
- Clubcard pricing: same as above; useful when you need to compare loyalty and standard prices.
- Product name, brand, category: same extraction path; good stable keys for joining records over time.
- Allergen info, ingredient list, nutritional data: same extraction path; check the rendered page because these blocks can be collapsed behind tabs.
- Customer ratings, review counts, review text: same extraction path; review text may require scrolling or a JavaScript scenario if reviews load on interaction.
- Geo-specific content: add country_code to route through a residential IP in that country.
- JavaScript-dependent content: render_js handles the page; stealth_proxy is the heavier option when bot detection blocks the request.
- Structured output: extract_rules with CSS selectors mapped to field names, or ai_extract_rules with a natural-language spec.
If a field is missing, first check whether it is behind an interaction (tab, accordion, lazy load) before changing extraction rules. A JavaScript scenario that clicks or scrolls can expose content that is present but not yet rendered.
How option choices change credit cost
Credit cost is driven by the options you enable, not by the Tesco URL itself. A plain request starts at 1 credit. JavaScript rendering costs 5 credits. Premium proxies cost 10 credits when JavaScript rendering is disabled and 25 credits when it is enabled. stealth_proxy costs 75 credits. API credits are valid for one month and do not roll over.
A practical consequence: if you are collecting a large catalogue, test whether render_js alone is enough before moving to stealth_proxy. The jump from 5 to 75 credits per request is large enough to change the shape of a project. Premium proxies sit between those two points, and the 10-versus-25 split means the same proxy option costs more once you also ask for rendering. If you only need a screenshot for a spot check, that is a different request type from a full data extraction run.
Plan concurrency separately from credits. Concurrency is the number of requests that can be sent at the same time, and it is set by your plan rather than by the target site.
Three different failure modes
It helps to separate three things that can look like 'the scraper is not working':
- Concurrency limit reached. The API rejects or queues requests because you have more in flight than your plan allows. Fix: reduce parallelism or move to a higher-concurrency plan.
- Target throttling. Tesco responds slowly or returns a challenge because request patterns are aggressive. Fix: space out requests or use multiple sessions.
- Anti-bot block. The page returns a challenge or incomplete content even at low volume. Fix: enable stealth_proxy or adjust rendering options.
Diagnosing which one you are hitting prevents wasted credit spend on heavier options when the real problem is simply too many parallel requests.
Example: one product page to structured JSON
Suppose you want price, unit price and Clubcard price for a single Tesco product URL. A workable request plan looks like this:
- Send the Tesco product URL with your API key.
- Enable render_js so the JavaScript-rendered price block is present.
- Attach extract_rules mapping CSS selectors to field names such as price, unit_price and clubcard_price.
- If selectors are unstable, switch to ai_extract_rules with a plain-language description of the fields you want.
- Parse the returned JSON and store the product URL alongside the record so you can re-request later.
Start with one URL and inspect the response before scaling to a catalogue. If the response is blocked rather than empty, move to stealth_proxy; if it is empty but not blocked, check whether the field needs a click or scroll first.
Getting from zero to a first request
The supplied workflow has four steps. Create an account to get an API key and the starting credits. Install an SDK for your stack, or use plain cURL. Send one HTTP call with your key and a Tesco URL; proxy rotation, fingerprint handling and JavaScript rendering happen on the provider side. Add advanced parameters only when the basic request is not enough.
SDKs are published for Python, Node.js, Go, PHP, Ruby and Java, and cURL works without an SDK. The dashboard request builder is a reasonable place to test a request before copying the generated snippet into your codebase. No Tesco account is required for the request itself.
Planning checklist before you scale
Use this checklist to avoid the common cost and reliability mistakes:
- Confirm which fields you actually need; do not enable stealth_proxy for fields that render fine with render_js.
- Decide whether you need geo-specific content; if not, skip country_code.
- Test extract_rules on two or three product pages with different layouts before running a catalogue.
- Estimate credits per request from the options you chose, then multiply by expected request volume.
- Check your plan's concurrency against your intended parallelism.
- Decide how often you will re-request each URL, since credits do not roll over month to month.
- Keep the source URL with each record so you can audit and re-fetch.
| Plan | Price | API credits | Concurrent requests | JavaScript rendering | Rotating & premium proxies | Geotargeting | Screenshots & extraction rules | Priority support | Account manager | Team management |
|---|---|---|---|---|---|---|---|---|---|---|
| Hobby | $19 /mo | 75,000 | 25 | Included | Included | Included | Included | Not included | Not included | Not included |
| Freelance | $49 /mo | 250,000 | 50 | Included | Included | Included | Included | Not included | Not included | Not included |
| Startup (Recommended) | $99 /mo | 1,000,000 | 100 | Included | Included | Included | Included | Not included | Not included | Not included |
| Business | $249 /mo | 3,000,000 | 200 | Included | Included | Included | Included | Included | Included | Included |
| Business + | $599 /mo | 8,000,000 | 400 | Included | Included | Included | Included | Included | Included | Included |
| Enterprise 14 | $999 /mo | 14,000,000 | 500 | Included | Included | Included | Included | Included | Included | Included |
| Enterprise 24 | $1,599 /mo | 24,000,000 | 600 | Included | Included | Included | Included | Included | Included | Included |
| Enterprise 41 (Recommended) | $2,399 /mo | 41,000,000 | 700 | Included | Included | Included | Included | Included | Included | Included |
| Enterprise 69 | $3,599 /mo | 69,000,000 | 800 | Included | Included | Included | Included | Included | Included | Included |
| Enterprise 120 | $5,799 /mo | 120,000,000 | 900 | Included | Included | Included | Included | Included | Included | Included |
Prices are exclusive of VAT. API credits are valid for one month and do not roll over; requests start at 1 credit each. This is a dated reference captured from the source; check current pricing before committing.
Frequently asked questions
Do I need a Tesco account to scrape Tesco?
No. You need an API key from the scraping provider, not a Tesco login. The request is sent with your key and a Tesco URL, and the provider handles proxies, browsers and anti-bot measures.
Can I target a specific country?
Yes. Pass country_code on the request to route through a residential IP in that country. This matters when the content shown varies by geography.
Is there a rate limit per Tesco URL?
The API enforces concurrency limits per plan rather than per-target rate limits. If Tesco throttles aggressive request patterns, space out requests or use multiple sessions.
How do I get structured JSON instead of HTML?
Use extract_rules with CSS selectors mapped to field names, or ai_extract_rules with a natural-language description of the fields you want. The response is returned as parsed JSON.
Which languages can I use?
Any language that can make an HTTP request. SDKs are published for Python, Node.js, Go, PHP, Ruby and Java, and plain cURL works too.
How much does a Tesco request cost in credits?
A plain request starts at 1 credit. JavaScript rendering costs 5 credits. Premium proxies cost 10 credits without JavaScript rendering and 25 credits with it. stealth_proxy costs 75 credits. Whether a free starting allowance applies, and whether a card is needed to begin, depend on the account terms in force when you sign up, so confirm those before budgeting a project.