Megekko APImegekko.be ↗
Access Megekko product catalog data via API: search products, browse categories, and retrieve specs, pricing, stock status, and EAN/MPN for Dutch electronics.
What is the Megekko API?
The Megekko API exposes 6 endpoints covering the full Megekko.nl Dutch electronics catalog, returning product names, EUR prices, stock status, EAN barcodes, manufacturer part numbers, and detailed specifications. Use search_products to run keyword queries across the entire catalog, get_product_details to pull structured specs and images for a single article, or list_products_by_category to paginate through any category path with optional filter strings.
curl -X GET 'https://api.parse.bot/scraper/cfb2fabb-ff95-421b-9430-4f87d251b83b/search_products?page=1&query=RTX+5070' \ -H 'X-API-Key: $PARSE_API_KEY'
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 megekko-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: Megekko SDK — search products, browse categories, get details."""
from parse_apis.megekko_product_api import Megekko, ProductNotFound
client = Megekko()
# Search for GPUs by keyword, capped at 5 results
for product in client.productsummaries.search(query="RTX 5070", limit=5):
print(product.name, product.price_str, product.stock_status)
# Drill into one product's full details via the summary→detail navigation
item = client.productsummaries.list_gpu(limit=1).first()
if item:
detail = item.details()
print(detail.name, detail.price, detail.brand, detail.availability)
# Browse a category by constructing it from its path
category = client.category("/Computer/Componenten/Processoren/Socket-AM5-Processoren")
for cpu in category.products(limit=3):
print(cpu.name, cpu.price, cpu.in_stock)
# Fetch a product directly by ID, with typed error handling
try:
gpu = client.products.get(id="297161")
print(gpu.name, gpu.price, gpu.currency)
for key, value in list(gpu.specs.items())[:3]:
print(f" {key}: {value}")
except ProductNotFound as exc:
print(f"Product not found: {exc}")
# List all categories available on the site
for cat in client.categories.list(limit=5):
print(cat.name, cat.path)
print("exercised: search / list_gpu / details / category.products / products.get / categories.list")
Full-text search over Megekko product catalog. Returns product summaries matching the query, ordered by relevance. Paginates server-side; each page returns up to ~50 results. No filters beyond the query string — finer selection is client-side over the returned list.
| Param | Type | Description |
|---|---|---|
| page | integer | Page number for pagination. |
| queryrequired | string | Search keyword (e.g. 'RTX 5070', 'AMD Ryzen', 'monitor 4k') |
{
"type": "object",
"fields": {
"page": "integer, current page number",
"query": "string, the search query used",
"products": "array of product summary objects with name, url, id, price, price_str, brand, in_stock, stock_status, specs_preview"
},
"sample": {
"data": {
"page": 1,
"query": "RTX 5070",
"products": [
{
"id": "297161",
"url": "https://www.megekko.nl/product/1963/297161/Nvidia-Videokaarten/Gigabyte-GeForce-RTX-5070-WINDFORCE-OC-12G-Videokaart",
"name": "Gigabyte GeForce RTX 5070 WINDFORCE OC 12G Videokaart",
"brand": null,
"price": null,
"in_stock": null,
"price_str": "629,-",
"stock_status": "Uit eigen voorraad leverbaar. Levertijd: 1 dag (vrijdag)",
"specs_preview": null
}
]
},
"status": "success"
}
}About the Megekko API
Search and Browse
search_products accepts a query string (e.g. 'RTX 5070', 'AMD Ryzen', 'monitor 4k') and returns paginated product summaries — up to ~50 results per page — including name, price, price_str, brand, in_stock, stock_status, and a specs_preview object. Pagination is handled via the page integer parameter. Filtering beyond the query is done client-side against the returned list. list_categories retrieves a flat list of all category names and paths from the site's navigation, which you can feed directly into list_products_by_category.
Category Browsing
list_products_by_category takes a category_path starting with / (e.g. /Computer/Componenten/Videokaarten) and returns up to 50 products per page alongside a subcategories array with name, path, and count fields. When the requested path is a parent category, the response also includes an active_subcategory field pointing to the auto-selected largest subcategory. An optional filters string (e.g. 'f_vrrd-3_s-populair_pp-50') mirrors URL filter parameters from the site and lets you control sort order and other facets.
Product Details
get_product_details accepts either a product_id (article number such as '297161') or a full product_url, and returns a comprehensive object: id, ean, mpn, url, name, brand, price (EUR float), specs (key-value specification pairs), images (array of URLs), and category. IDs returned from search_products or list_products_by_category can be passed directly to this endpoint.
Convenience Endpoints
list_gpu_products and list_cpu_products are pre-configured shortcuts for the Videokaarten and Processoren category paths respectively, both sorted by popularity. GPU results include subcategory breakdown by vendor (Nvidia, AMD, Workstation); CPU results break down by socket type. Both support page pagination and return the same product summary shape as the general category endpoint.
The Megekko API is a managed, monitored endpoint for megekko.be — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when megekko.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 megekko.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?+
Is this an official API from the source site?+
Can I fix or extend this API myself if I need a new endpoint or field?+
What happens if I call an endpoint that has an issue?+
- Track EUR price changes and stock availability for specific GPU or CPU article numbers using
get_product_details. - Build a price comparison tool by searching the same keyword across multiple Dutch electronics retailers and comparing
pricefields. - Aggregate EAN and MPN identifiers from
get_product_detailsto cross-reference products against other European retailer catalogs. - Monitor whether a specific product is
in_stockby pollingsearch_productsorget_product_detailson a schedule. - Populate a product database with structured specs by iterating
list_products_by_categoryacross all paths returned bylist_categories. - Analyze GPU market inventory by fetching
list_gpu_productssubcategory counts for Nvidia and AMD segments. - Retrieve product images and specification key-value pairs from
get_product_detailsto populate a product feed or comparison table.
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 100 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 100 req/min |
One credit = one API call regardless of which marketplace API you call. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does Megekko offer an official public developer API?+
What does `get_product_details` return that the search and category endpoints do not?+
get_product_details returns the full specs object (all key-value specification pairs), images array, ean barcode, and mpn manufacturer part number. The search_products and list_products_by_category endpoints return only a specs_preview subset alongside name, price, brand, and stock status.Can I filter `search_products` results by price range or brand on the server side?+
search_products. The endpoint returns up to ~50 results per page and any narrowing by price range, brand, or other attributes must be applied client-side. list_products_by_category does accept a filters string parameter that can control sort order and facets when browsing by category path.Does the API expose seller reviews, user ratings, or product review counts for items?+
How does pagination work, and is there a total result count returned?+
search_products, list_products_by_category, list_gpu_products, list_cpu_products) paginate server-side, returning up to ~50 products per page via the integer page parameter. The responses do not currently include a total result count or total page count field, so you iterate pages until a shorter-than-expected or empty products array is returned.