Co APIbug.co.il ↗
Access Bug.co.il product search, category listings, detailed specs, pricing, and homepage promotions via a single API. Covers Israel's major electronics retailer.
What is the Co API?
The Bug.co.il API exposes 5 endpoints covering product search, category browsing, detailed product pages, and homepage promotions from Israel's Bug electronics retail site. Starting with search_products, you can query by keyword and receive paginated results with current and original pricing, brand, and image URLs — making it straightforward to track prices or build product feeds against Bug's catalog.
curl -X GET 'https://api.parse.bot/scraper/90a92f35-9919-4037-8945-0dc0f4d3ed6c/search_products?page=1&query=laptop' \ -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 bug-co-il-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: Bug.co.il electronics store — search, browse categories, get details."""
from parse_apis.bug_co_il_electronics_store_api import Bug, CategorySlug, ProductNotFound
client = Bug()
# Search for products across the catalog, capped at 5 results.
for product in client.products.search(query="laptop", limit=5):
print(product.name, product.current_price, product.brand)
# Drill into the first result's full details (description, specs, images).
product = client.products.search(query="samsung", limit=1).first()
if product:
detail = product.details()
print(detail.name, detail.current_price, detail.description)
# Browse a category by constructing it from its slug enum.
category = client.category(slug=CategorySlug.SMARTPHONES)
for phone in category.products(limit=3):
print(phone.name, phone.current_price, phone.url)
# Get homepage featured products and banners.
homepage = client.homepages.get()
for featured in homepage.featured_products[:3]:
print(featured.name, featured.current_price)
for banner in homepage.banners[:2]:
print(banner.title, banner.url)
# List all available categories.
for cat in client.categories.list(limit=5):
print(cat.name, cat.slug)
# Handle a product-not-found error gracefully.
try:
bad = client.product(url="https://www.bug.co.il/nonexistent/product/xyz")
bad.details()
except ProductNotFound as exc:
print(f"Product not found: {exc.product_url}")
print("exercised: products.search / product.details / category.products / homepages.get / categories.list")
Full-text search over the entire product catalog. Returns a paginated list of products matching the query keyword. Each product includes name, brand, pricing, URL, and thumbnail image. Paginates via integer page number; has_next indicates whether additional pages exist.
| Param | Type | Description |
|---|---|---|
| page | integer | Page number for pagination (1-indexed). |
| queryrequired | string | Search keyword to find products (e.g. 'laptop', 'smartphone', 'samsung') |
{
"type": "object",
"fields": {
"page": "integer, current page number",
"count": "integer, number of products on the current page",
"has_next": "boolean, whether more pages are available",
"products": "array of product objects with name, current_price, original_price, url, brand, image_url"
},
"sample": {
"data": {
"page": 1,
"count": 30,
"has_next": true,
"products": [
{
"url": "https://www.bug.co.il/brand/hp/color/naturalsilver/laptop/15/fd0034nj/9w848ea",
"name": "Laptop 15-fd0034nj",
"brand": "HP",
"image_url": "https://www.bug.co.il/images/site/manufacturer-preview-lazy.jpg",
"current_price": "2,499 ₪",
"original_price": null
}
]
},
"status": "success"
}
}About the Co API
Search and Category Browsing
The search_products endpoint accepts a required query string and an optional page integer, returning an array of product objects that each include name, current_price, original_price, url, brand, and image_url. The has_next boolean tells you whether additional pages exist, so you can walk through results programmatically. The get_category_products endpoint works the same way but takes a category_slug instead of a keyword — slugs like laptops, smartphones, or headphones are sourced directly from get_all_categories, which returns a flat list of all available category names and their corresponding slugs.
Product Detail and Specs
get_product_details takes a full product URL (as returned in the url field from search or category results) and returns a richer payload: a specs object containing key-value pairs of technical specifications, an images array, a description string (nullable), and both current_price and original_price. This is the only endpoint that exposes structured spec data, so price-comparison or product-information use cases will typically chain a listing endpoint into this one.
Homepage Promotions
get_homepage_featured requires no inputs and returns two arrays: banners (each with url, image, and title) and featured_products (same shape as listing endpoints). This reflects the active promotions Bug is running at query time, which makes it useful for monitoring deal cycles or surfacing current discounts.
Pagination and Coverage
All listing endpoints (search_products, get_category_products) paginate via an integer page parameter and signal continuation through has_next. There is no bulk-download or offset parameter beyond page number. The API covers publicly visible product data from bug.co.il; content that requires a logged-in account — such as saved wishlists or order history — is not included.
The Co API is a managed, monitored endpoint for bug.co.il — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when bug.co.il 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 bug.co.il 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 price drops on specific products by polling
get_product_detailsand comparingcurrent_priceagainstoriginal_price. - Build a Hebrew-language electronics price-comparison tool using
search_productsacross multiple keyword queries. - Monitor Bug's active promotions and featured deals by periodically calling
get_homepage_featured. - Populate a product catalog for a specific segment (e.g. headphones) using
get_category_productswith the relevant slug fromget_all_categories. - Aggregate structured specs from
get_product_detailsto compare technical attributes across laptop or smartphone models. - Alert on new category additions by diffing the
categoriesarray returned byget_all_categoriesover time. - Identify which brands appear most frequently in a category by aggregating the
brandfield across paginatedget_category_productsresults.
| 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 Bug.co.il offer an official developer API?+
What does `get_product_details` return that listing endpoints don't?+
get_product_details adds a specs object with structured key-value technical specifications, an images array with multiple image URLs, and a description string. Listing endpoints (search_products, get_category_products) return only name, current_price, original_price, url, brand, and image_url per product.Does the API expose customer reviews or ratings for products?+
How does pagination work across the listing endpoints?+
search_products and get_category_products accept an optional page integer (defaulting to the first page). Each response includes a count of products on the current page and a has_next boolean. There is no offset parameter or page-size control beyond incrementing the page number.Does the API cover stock availability or inventory status?+
current_price, original_price), product metadata, and specs, but no in-stock or inventory quantity field is exposed. You can fork this API on Parse and revise it to add stock status if that field is available on the product page.