KaBuM Scraper avatar

KaBuM Scraper

Pricing

Pay per event

Go to Apify Store
KaBuM Scraper

KaBuM Scraper

Scrape KaBuM products, prices, discounts, stock, sellers, ratings, and category data for Brazilian ecommerce intelligence.

Pricing

Pay per event

Rating

0.0

(0)

Developer

Stas Persiianenko

Stas Persiianenko

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

4 days ago

Last modified

Categories

Share

Scrape KaBuM product listings, prices, availability, seller details, ratings, and discount signals from Brazil's major technology and gaming ecommerce store.

What does KaBuM Scraper do?

KaBuM Scraper collects public product data from KaBuM search, category, and product pages.

It is designed for ecommerce monitoring, price intelligence, assortment research, and affiliate content workflows.

The actor reads KaBuM pages over HTTP and extracts the structured product data embedded in the page.

You can start from search terms, direct KaBuM URLs, or a mix of both.

Who is it for?

๐Ÿ›’ Ecommerce and retail teams

Use KaBuM Scraper to monitor Brazilian electronics prices, compare first-party and marketplace offers, and keep internal dashboards current without manual checks.

Typical workflow:

  1. Run daily searches for priority terms such as notebook, ssd, or monitor gamer.
  2. Join repeated runs by productId.
  3. Alert your team when priceWithDiscount, available, or sellerName changes.

๐Ÿ“Š Market intelligence and category analysts

Track technology categories, brand coverage, discount patterns, and product availability across one of Brazil's most important electronics retailers.

Typical workflow:

  1. Scrape category or search URLs weekly.
  2. Group products by brand, category, and sellerName.
  3. Export the dataset to BigQuery, Sheets, or your BI tool for trend reporting.

๐Ÿงพ Repricing and assortment operations

Use structured price and availability data to compare SKUs, watch competitor movement, and prioritize manual review of fast-changing products.

Typical workflow:

  1. Provide the KaBuM URLs or product-focused searches your team cares about.
  2. Compare currentPrice, priceWithDiscount, originalPrice, and stockQuantity.
  3. Feed the results into repricing, inventory, or merchandising workflows.

โœ๏ธ Affiliate publishers and content teams

Refresh product comparison tables for electronics, gaming, PC parts, and peripherals with current names, prices, images, and links.

Typical workflow:

  1. Run a small search for a buying guide topic.
  2. Export name, url, imageUrl, prices, rating, and availability.
  3. Update articles, product cards, or affiliate research sheets.

๐Ÿง‘โ€๐Ÿ’ป Developers and automation builders

Call the actor from the Apify API, webhooks, or MCP tools when you need clean KaBuM product data in another app.

Typical workflow:

  1. Trigger a run from Node.js, Python, cURL, Zapier, Make, or an MCP-compatible assistant.
  2. Read the default dataset by API.
  3. Store normalized product records in your application.

Why use this actor?

KaBuM is a key retailer for computers, components, peripherals, games, and electronics in Brazil.

Manual price checks are slow and hard to repeat.

This actor turns those public pages into a structured dataset with product IDs, prices, stock, seller, and rating fields.

What data can you extract?

FieldDescription
productIdKaBuM product code
nameProduct title
urlProduct detail URL
imageUrlMain product image
brandManufacturer name when available
categoryKaBuM category path
sellerNameSeller or fulfillment name
currentPriceListed price
priceWithDiscountDiscount or cash price
originalPricePrevious/list price
primePriceKaBuM Prime price when available
discountPercentageDisplayed discount percentage
maxInstallmentInstallment text
ratingProduct rating
reviewCountRating count
availableAvailability flag
stockQuantityQuantity exposed by KaBuM
isMarketplaceMarketplace flag
isFreeShippingFree shipping flag
sourceUrlPage used for extraction
searchQuerySearch query inferred from URL
scrapedAtExtraction timestamp

How much does it cost to scrape KaBuM products?

The actor uses pay-per-event pricing.

You pay a small run-start fee plus a per-product result fee. The current local pricing configuration is:

ChargeAmount
Run start$0.005 per run
Product result, FREE tier$0.000028343 per product
Product result, BRONZE tier$0.000024646 per product
Product result, SILVER tier$0.000019224 per product
Product result, GOLD tier$0.000014788 per product
Product result, PLATINUM tier$0.0000098585 per product
Product result, DIAMOND tier$0.0000069009 per product

Example run costs on the FREE tier:

Example runFormulaEstimated actor charge
First test with 20 products$0.005 + 20 ร— $0.000028343about $0.0056
Daily price check with 100 products$0.005 + 100 ร— $0.000028343about $0.0078
Category snapshot with 1,000 products$0.005 + 1,000 ร— $0.000028343about $0.0333
Large assortment export with 10,000 products$0.005 + 10,000 ร— $0.000028343about $0.2884

Free-plan estimate: with roughly $5 of Apify platform credits, the actor charge alone would cover about 176,000 FREE-tier product results if you ran one large batch. Real usage can be lower after platform compute, proxy, and storage costs, so keep your first run small with the default maxItems value and increase it when the output matches your workflow.

How to scrape KaBuM search results

  1. Open the actor on Apify.
  2. Add one or more search terms, for example notebook, ssd, or placa de video.
  3. Set maxItems to the number of products you need.
  4. Run the actor.
  5. Export the dataset as JSON, CSV, Excel, or through the API.

How to scrape KaBuM URLs

Paste KaBuM search, category, or product URLs into startUrls.

You can combine URLs with search terms in the same run.

The actor deduplicates products by KaBuM product ID.

Input configuration

Search terms

Use queries for simple keyword monitoring.

Examples:

  • notebook
  • ssd
  • monitor gamer
  • placa de video

Start URLs

Use startUrls when you already have a KaBuM page URL.

Examples include search URLs, category URLs, and product URLs.

Maximum products

Use maxItems to control output size and cost.

The default prefill is intentionally low for safe first runs.

Request retries

Use maxRequestRetries to control retry behavior for temporary network errors.

Most users can keep the default value.

Example input

{
"queries": ["notebook", "ssd"],
"startUrls": [
{ "url": "https://www.kabum.com.br/busca/placa-de-video" }
],
"maxItems": 50,
"maxRequestRetries": 3
}

Example output

{
"productId": "952233",
"name": "Notebook Acer Aspire 5...",
"url": "https://www.kabum.com.br/produto/952233/...",
"brand": "Acer",
"category": "Computadores/Notebooks/Notebook Acer",
"sellerName": "KaBuM!",
"currentPrice": 3555.54,
"priceWithDiscount": 3199.99,
"discountPercentage": 10,
"available": true,
"stockQuantity": 124,
"sourceUrl": "https://www.kabum.com.br/busca/notebook",
"searchQuery": "notebook",
"scrapedAt": "2026-05-16T00:00:00.000Z"
}

Tips for better results

  • โœ… Use Portuguese product terms used by Brazilian shoppers.
  • โœ… Start with broad categories, then add specific searches.
  • โœ… Use product IDs to deduplicate data across recurring runs.
  • โœ… Track priceWithDiscount for cash/discount price monitoring.
  • โœ… Track stockQuantity and available for availability alerts.

Common use cases

Price monitoring

Run the actor daily and compare priceWithDiscount by productId.

Assortment tracking

Collect category pages to see which brands and product families are present.

Affiliate content updates

Export product names, prices, image URLs, and links for product comparison pages.

Competitive intelligence

Monitor KaBuM marketplace and first-party seller changes over time.

Integrations

Use the Apify dataset API to send results to your data warehouse.

Connect Apify with Make, Zapier, Google Sheets, BigQuery, or your own webhook pipeline.

Common workflow patterns:

  • KaBuM Scraper โ†’ Dataset โ†’ Google Sheets dashboard.
  • KaBuM Scraper โ†’ Webhook โ†’ repricing alert.
  • KaBuM Scraper โ†’ BigQuery โ†’ historical price model.
  • KaBuM Scraper โ†’ API client โ†’ affiliate site refresh.

API usage with Node.js

import { ApifyClient } from 'apify-client';
const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('automation-lab/kabum-scraper').call({
queries: ['notebook'],
maxItems: 20
});
console.log(run.defaultDatasetId);

API usage with Python

from apify_client import ApifyClient
client = ApifyClient('YOUR_APIFY_TOKEN')
run = client.actor('automation-lab/kabum-scraper').call({
'queries': ['ssd'],
'maxItems': 20,
})
print(run['defaultDatasetId'])

API usage with cURL

curl "https://api.apify.com/v2/acts/automation-lab~kabum-scraper/runs?token=$APIFY_TOKEN" \
-H 'Content-Type: application/json' \
-d '{"queries":["monitor gamer"],"maxItems":20}'

MCP usage

You can run this actor from MCP-compatible tools through Apify MCP.

Use this tools URL:

https://mcp.apify.com/?tools=automation-lab/kabum-scraper

Add it to Claude Code with the HTTP transport:

$claude mcp add apify-kabum --transport http "https://mcp.apify.com/?tools=automation-lab/kabum-scraper"

For Claude Desktop, add this to your MCP server configuration file and restart the app:

{
"mcpServers": {
"apify-kabum": {
"type": "http",
"url": "https://mcp.apify.com/?tools=automation-lab/kabum-scraper"
}
}
}

For Cursor, open Cursor settings, go to MCP servers, choose Add new global MCP server, and use this JSON:

{
"mcpServers": {
"apify-kabum": {
"type": "http",
"url": "https://mcp.apify.com/?tools=automation-lab/kabum-scraper"
}
}
}

For VS Code MCP-compatible extensions, create or update the workspace MCP configuration with the same HTTP server entry:

{
"servers": {
"apify-kabum": {
"type": "http",
"url": "https://mcp.apify.com/?tools=automation-lab/kabum-scraper"
}
}
}

Example prompts:

  • "Run KaBuM Scraper for notebooks and summarize the cheapest Acer models."
  • "Scrape SSD results from KaBuM and create a price comparison table."
  • "Check whether the selected product IDs are still available on KaBuM."

Data quality notes

The actor extracts structured data embedded in KaBuM pages.

Some fields are optional because KaBuM does not expose every value for every product.

For example, Prime prices, free shipping flags, or ratings may be missing on some products.

Limitations

The actor currently focuses on public product data.

It does not log in, add products to cart, bypass private user pricing, or access account-only data.

Pagination depth depends on the data exposed in the supplied page and the selected maxItems value.

FAQ

Why did I get fewer products than requested?

The source page may expose fewer unique products than your maxItems limit, or several inputs may overlap and deduplicate to the same product IDs.

Why is a price field empty?

KaBuM exposes several price variants. Some products may not have Prime prices, original prices, or discounts at the time of scraping.

Should I use queries or start URLs?

Use queries for keyword monitoring and start URLs when you need a specific KaBuM page.

Legality and ethical use

This actor collects publicly available product information.

Always review KaBuM's terms, respect applicable laws, and use the data responsibly.

Do not use scraped data for spam, fraud, or abusive automation.

Explore other ecommerce actors from Automation Lab:

Support

If a run fails or returns unexpected data, open an issue from the Apify run page.

Include the input, run ID, and a short description of what you expected.

Changelog

0.1

Initial KaBuM product search and URL scraping release.

Field reference

productId is the stable key to join repeated runs.

url points to the KaBuM product page.

sourceUrl records where the product was found.

scrapedAt makes recurring monitoring easier.

isMarketplace helps separate KaBuM first-party and marketplace offers.

stockQuantity can change quickly and should be treated as point-in-time data.

Operational recommendations

Run small tests before scheduling large recurring jobs.

Store historical snapshots if you need price change detection.

Export to CSV for manual review or JSON for automated pipelines.

Use Apify webhooks when you need alerts after every run.