Tesco API reference
Compare Tesco shelf prices by pack, then check the product behind each Tesco link or TPNC.
The Tesco API has 4 endpoints, called the same way: POST /execute with the endpoint ID as capability and its fields as input, or pin Tesco in the MCP server and call each one as a tool. The data comes back as JSON in results[0].data, with what the call cost in billing.credits_charged.
Prices run from 1–8 credits to 2 credits per call, and a failed call costs nothing.
Endpoints
Open an endpoint for its input, the fields it returns and the request in cURL, Python and Node.js.
| Endpoint | What it returns | Price |
|---|---|---|
tesco.category.products.list |
Pass a category facet to collect one page of Tesco products. | 1–8 credits |
tesco.product.detail.get |
Send a Tesco product link or TPNC to read its price, description and product information where supplied. | 1 credit |
tesco.categories.list |
Read Tesco’s nested category tree, then reuse the returned facet for the category you want to collect. | 2 credits |
tesco.products.search |
Search Tesco Groceries UK by keyword and return ranked product ids and canonical product URLs for one results page. | 1 credit |
What to know
- Keep the TPNC with every record TPNC identifies the product in a Tesco link. Save it alongside the pack title; a similar title alone is not enough to match packs.
- Pack price and unit price answer different questions Compare the price of the whole pack first. For value comparisons, keep Tesco’s unit price together with its unit, such as each or kilogram.
- Read an offer with its conditions Keep the promotion text, dates and membership or quantity conditions. Check the dates before reporting an offer as current; retain the ordinary pack price separately.
- Category order is not keyword search rank The page follows a category’s returned order. It does not measure where a pack ranks for a shopper’s search term.
Something missing or unclear? Ask the team that builds the Tesco endpoints.