Discover/Lidl API
live

Lidl APIlidl.be

Search and retrieve product metadata, prices, promotions, and Lidl Plus discounts from Lidl Belgium's catalog via 2 structured JSON endpoints.

This API takes change requests — .
Endpoint health
monitored
get_product
search_products
Checks pendingself-healing
Endpoints
2
Updated
3h ago

What is the Lidl API?

The Lidl Belgium API provides 2 endpoints to search and retrieve product data from lidl.be, returning up to 1,000 products per request with fields covering price, brand, category, availability, and promotional ribbons. Use search_products to query by name, brand, or numeric product ID, and get_product to pull detailed metadata — including Lidl Plus member pricing — for a specific item by ID.

This call costs1 credit / call— charged only on success
Try it
Maximum number of products to return per page (max 1000).
Search term — a product name (e.g. 'chocolat'), brand (e.g. 'KINDER'), or numeric product ID (e.g. '10029289').
Number of results to skip for pagination.
api.parse.bot/scraper/393f388e-ff29-4ce1-96d8-3451bcc161ad/<endpoint>
Ready to send
Fill in the parameters and hit sign in to send to see live response data here.
Call it over HTTPgrab a free API key at signup
curl -X GET 'https://api.parse.bot/scraper/393f388e-ff29-4ce1-96d8-3451bcc161ad/search_products?query=chocolat&limit=36&offset=0' \
  -H 'X-API-Key: $PARSE_API_KEY'
Python SDK · recommended

Typed, relational, agent-ready

A generated client with real types, enums, and the links between objects — the structure a flat JSON response can't carry. Autocompletes in your editor and reads cleanly to coding agents.

  • Fully typed · autocompletes
  • Objects link to objects
  • Typed errors & pagination

Typed Python client. Set up the SDK in your uv project, then pull this API’s typed client:

uv add parse-sdk
uv run parse init
uv run parse add --marketplace lidl-be-api

uv run parse add --marketplace pulls a pinned snapshot of this canonical API — it won’t change underneath you. To customize it, subscribe and swap to your own copy.

"""Walkthrough: Lidl Belgium product search — bounded, re-runnable."""
from parse_apis.lidl_be_api import LidlBe, ProductNotFound

client = LidlBe()

# Search for chocolate products, cap total items fetched.
for product in client.products.search(query="chocolat", limit=5):
    print(product.title, product.brand, product.price, product.currency)

# Drill into the first search hit for full detail.
hit = client.products.search(query="KINDER", limit=1).first()
if hit is not None:
    detail = client.products.get(product_id=hit.id)
    print(detail.title, detail.price, detail.base_price_text)
    print("available online:", detail.available_online)
    print("available in store:", detail.available_in_store)

# Handle a missing product gracefully.
try:
    client.products.get(product_id="0000000")
except ProductNotFound as e:
    print("not found:", e.message)

print("exercised: products.search / products.get / ProductNotFound")
All endpoints · 2 totalmissing one? ·

Search for products on Lidl Belgium by query term (product name, brand, category keyword) or exact product ID. Returns paginated results with product metadata, prices, and promotion information. When the query matches an exact product ID, the result contains a single product with full details. Pagination is controlled by offset and limit parameters; omitting them returns the first 36 results.

Input
ParamTypeDescription
limitintegerMaximum number of products to return per page (max 1000).
queryrequiredstringSearch term — a product name (e.g. 'chocolat'), brand (e.g. 'KINDER'), or numeric product ID (e.g. '10029289').
offsetintegerNumber of results to skip for pagination.
Response
{
  "type": "object",
  "fields": {
    "limit": "Requested page size",
    "query": "The search query that was executed",
    "total": "Total number of matching products",
    "offset": "Current pagination offset",
    "products": "Array of product objects with id, title, brand, category, price, currency, old_price, base_price_text, image_url, url, available_online, available_in_store, availability_badge, ribbons, and lidl_plus"
  },
  "sample": {
    "data": {
      "limit": 36,
      "query": "chocolat",
      "total": 51,
      "offset": 0,
      "products": [
        {
          "id": "10029289",
          "url": "https://www.lidl.be/p/fr-BE/kinder-schokobons-chocolat-blanc/p10029289",
          "brand": "KINDER",
          "price": 3.89,
          "title": "KINDER Schokobons chocolat blanc",
          "ribbons": [],
          "category": "Actie op is op ",
          "currency": "EUR",
          "image_url": "https://imgproxy-retcat.assets.schwarz/Tqrlpm_8KbHhsqQL9Q7XqUAisrXOcQwGk5KP3ZQ7gzw/sm:0/exar:1:ce/w:427/h:320/cz/M6Ly9wcm9kLWNhd/GFsb2ctbWVkaWEvaW50LzI4NzMyM0JCQzMzMkI0NDg3NjFBOEVFN0/MwOUY4RDVFQjVEODhBOTQ1MkY5MTlCMjY1QzdFRTc4RDZDOTE0QzAucG5n.png",
          "lidl_plus": null,
          "old_price": null,
          "base_price_text": "200 g - 19,45 EUR/kg",
          "available_online": false,
          "availability_badge": "Uniquement en magasin le 12/08 - 18/08",
          "available_in_store": true
        }
      ]
    },
    "status": "success"
  }
}

About the Lidl API

Endpoints and Data Coverage

The search_products endpoint accepts a query parameter (product name, brand keyword, or numeric product ID) and returns a paginated list of matching items. Each product object includes id, title, brand, category, price, currency, old_price, base_price_text, image_url, url, and availability status. Pagination is controlled via limit (up to 1,000) and offset parameters, and the response includes a total count to support cursor-style iteration.

Product Detail

The get_product endpoint accepts a single product_id — a numeric string obtainable from search_products results — and returns the full detail record for that item. In addition to the standard metadata fields (title, brand, price, category, image_url, url), it surfaces ribbons (an array of promotional label texts such as discount banners or special offer tags) and lidl_plus, which carries Lidl Plus member discount information when applicable for that product.

Currency and Regional Scope

All prices are denominated in EUR and sourced from the Belgian storefront at lidl.be. The catalog reflects Belgian product assortment, which may differ from Lidl storefronts in other countries. Both endpoints always return currency: "EUR". The old_price field, when present, indicates a previous price against which the current price represents a reduction.

Reliability & maintenance

The Lidl API is a managed, monitored endpoint for lidl.be — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when lidl.be changes and a check fails, the API is automatically queued for repair and re-verified. It is built to keep working as the site underneath it changes.

This isn't an official lidl.be API — it's an independent, maintained REST wrapper over public data. Where the source has no official API (or only a limited one), Parse gives you a stable contract over a source that never promised one, and keeps it current. Need a new endpoint or field? You can revise it yourself in plain English and the agent rebuilds it against the live site in minutes — contributing the change back to the shared API is free.

Will this API break when the source site changes?+
It's built not to. Every endpoint is health-checked on a schedule with automated test probes. When the source site changes and a check fails, the API is automatically queued for repair and re-verified — that's the self-healing layer. Each API page shows when its endpoints were last verified. And because marketplace APIs are shared, any fix reaches everyone using it.
Is this an official API from the source site?+
No — Parse APIs are independent, managed REST wrappers over publicly available data. That is the point: where a site has no official API (or only a limited one), Parse gives you a maintained, monitored endpoint for that data and keeps it working as the site changes — so you get a stable contract over a source that never promised one.
Can I fix or extend this API myself if I need a new endpoint or field?+
Yes — and you don't have to wait on us. This API was generated by the Parse agent, which stays attached. Describe the change in plain English ("add an endpoint that returns reviews", "fix the price field") in the revise box on the API page or via the revise_api MCP tool, and the agent rebuilds it against the live site in minutes. Contributing the change back to the public API is free.
What happens if I call an endpoint that has an issue?+
Errors are machine-readable: a bad call returns a clean status with the list of available endpoints and a repair hint, so an agent (or you) can recover or trigger a fix instead of failing silently. Confirmed failures feed the automatic repair queue.
Common use cases
  • Track price drops on specific products by comparing price against old_price over time
  • Monitor Lidl Plus member discounts via the lidl_plus field across product categories
  • Build a Belgian grocery price comparison tool using search_products with category keywords
  • Aggregate promotional ribbon labels from ribbons to surface active deals and special offers
  • Sync Lidl Belgium's catalog into an internal product database using paginated search_products calls with limit and offset
  • Resolve a product ID from search results and fetch enriched detail via get_product for listing pages
  • Alert users when a watched brand's products appear in promotions using brand-based queries
Pricing & limitsSee full pricing →
TierPriceCredits/monthRate limit
Free$0/mo2005 req/min
Hobby$30/mo1,00020 req/min
Developer$100/mo5,000100 req/min
Team$300/mo20,000300 req/min
Company$1,000/mo100,000500 req/min

Each endpoint has a fixed posted price per successful call — most fall between 1 and 10 credits — shown on this API's page before you run it. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.

Frequently asked questions
Does Lidl Belgium offer an official public developer API?+
Lidl does not publish a public developer API for lidl.be. There is no documented REST or GraphQL interface available to third-party developers for accessing the Belgian storefront's catalog data.
What does the `search_products` endpoint return when a numeric product ID is passed as the query?+
When the query parameter is a numeric product ID (e.g. '10029289'), the endpoint returns a single matching product with its full metadata. This is useful for quickly resolving product details without calling get_product separately, though get_product provides additional fields like ribbons and lidl_plus.
Does the API return stock levels or in-store availability?+
The API returns an available_online field indicating online availability status, but does not expose store-level inventory, click-and-collect availability, or stock quantities. You can fork the API on Parse and revise it to add store-level availability if that data becomes accessible.
Does the API cover Lidl storefronts in other countries, such as lidl.de or lidl.nl?+
No — the API covers only the Belgian storefront at lidl.be. Product assortment, pricing, and promotions on this endpoint are specific to Belgium and priced in EUR. You can fork the API on Parse and revise it to target another country's Lidl domain.
Are customer reviews or product ratings available through this API?+
Not currently. The API covers product metadata, pricing, promotional ribbons, and Lidl Plus discount info, but does not include customer reviews or star ratings. You can fork the API on Parse and revise it to add a reviews endpoint if that data is exposed on product pages.
Page content last updated . Spec covers 2 endpoints from lidl.be.
Related APIs in EcommerceSee all →