verkkokauppa.com APIverkkokauppa.com ↗
Access Verkkokauppa.com product data via API: search, pricing, availability, reviews, outlet/clearance listings, and full category browsing across Finland's largest electronics retailer.
curl -X GET 'https://api.parse.bot/scraper/e51a9cee-df5a-492b-bb34-75d4f2a85f7e/search_products?page=1&sort=-score&query=laptop' \ -H 'X-API-Key: $PARSE_API_KEY'
Search for products by keyword query on Verkkokauppa.com. Returns paginated results with product data, included category/campaign details, and pagination metadata.
| Param | Type | Description |
|---|---|---|
| page | integer | Page number (1-indexed). |
| sort | string | Sort order. Accepted values: -score, -popularity, price, -price. |
| queryrequired | string | Search keyword. |
{
"type": "object",
"fields": {
"data": "array of product objects with attributes including name, price, images, rating, and category relationships",
"meta": "object containing totalResults and search variant info",
"included": "array of related resources such as sales categories, brands, and campaigns"
},
"sample": {
"data": {
"data": [
{
"id": "1014773",
"type": "products",
"attributes": {
"name": "HP Laptop 17-cn3014no",
"price": {
"current": 479.99,
"original": 479.99
}
}
}
],
"meta": {
"totalResults": 500
},
"included": [
{
"id": "laptops",
"type": "salesCategories"
}
]
},
"status": "success"
}
}About the verkkokauppa.com API
The Verkkokauppa.com API provides 11 endpoints covering product search, detailed specs, real-time pricing, store-level stock availability, customer reviews, and category/sale/outlet browsing for Finland's largest electronics retailer. The get_product_details endpoint alone returns name, brand, description, specifications, images, price, and warehouse availability in a single call, while get_store_availability breaks down stock by shipment, pickup, and individual store locations.
Product Search and Filtering
The search_products endpoint accepts a query string and an optional sort parameter (-score, -popularity, price, -price) and returns paginated data arrays of product objects alongside included resources such as brands, sales categories, and campaigns. For more targeted queries, search_with_filters adds a filters input that accepts a JSON string of attribute key-value pairs — for example {"base+brand": "Samsung"} — allowing brand or attribute-scoped searches without a keyword. Both endpoints expose meta.totalResults for building pagination controls.
Product Details, Pricing, and Availability
get_product_details returns a single product's full attribute set: name, description, brand, price, specifications, images, and an availability object with warehouse and store-level stock data, plus rating_stats containing review count, average rating, and rating distribution. When only price and availability are needed, get_product_price_and_availability provides a lighter payload with current and original prices, tax rate, and any active discount details without the full spec overhead.
get_store_availability returns a dedicated availability snapshot per product, including boolean flags (isReleased, isSoldOut, isShippingAllowed) and a stocks object broken into shipment, pickup, and per-store sub-objects, each with individual counts and availability flags. An updatedAt ISO timestamp indicates data freshness.
Categories, Sales, Outlet, and Reviews
get_category_list returns the full category tree as data (top-level categories with label, slug, and productCount) and included child categories, giving you the category_id slugs needed by get_category_products. The search_products_on_sale and get_clearance_products endpoints surface discount-priced items; get_outlet_products specifically covers customer-return stock and adds an outlet-specific customerReturnsInfo and condition field to each product object. Note that outlet and review endpoints return a 0-indexed pageNo in the response, even though they accept 1-indexed page input.
get_product_reviews returns an array of reviews objects, each with rating, reviewText, userNickname, submissionTime, and secondaryRatings. Products with no reviews return an empty array with totalItems: 0. Reviews may include syndicated content from related product variants.
- Track real-time price drops on specific product IDs using
get_product_price_and_availabilityfor deal-alert tooling. - Build a Finnish electronics price comparison tool by pulling search results across multiple category slugs from
get_category_products. - Monitor per-store stock levels with
get_store_availabilityto surface which Helsinki or Tampere locations have an item in stock for pickup. - Aggregate customer review sentiment using
reviewTextandratingfields fromget_product_reviewsacross product categories. - Populate a deal-discovery feed by combining
search_products_on_sale,get_clearance_products, andget_outlet_productsfor discount and return stock. - Sync a product catalog with full specs and images by iterating categories via
get_category_listand fetching details throughget_product_details. - Filter competitor or brand-specific listings using the
filtersparameter insearch_with_filterswith abase+brandkey.
| 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 | 250 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 Verkkokauppa.com have an official public developer API?+
What does get_outlet_products return that regular search endpoints don't?+
customerReturnsInfo and condition fields specific to returned stock, and the response uses a distinct schema with pageNo (0-indexed), numPages, totalItems, and a products array — rather than the data/meta/included structure used by search and category endpoints.Does the API cover product questions and answers, or seller/third-party listings?+
How does pagination work across different endpoints?+
page integer and return meta.totalResults. The get_outlet_products and get_product_reviews endpoints also accept 1-indexed page input but return a 0-indexed pageNo in the response along with numPages and totalItems, so callers should use the response numPages field rather than inferring page count from totalResults.