Flanco APIflanco.ro ↗
Access Flanco.ro product search, category listings, product details, reviews, and store locations via a structured JSON API for Romania's electronics retailer.
What is the Flanco API?
The Flanco.ro API covers 6 endpoints that expose product data, customer reviews, and physical store information from Romania's Flanco electronics retail chain. Using search_products, you can query the catalog by keyword and receive product IDs, names, prices, URLs, and stock availability in a single response. The API also exposes the full category hierarchy, paginated category listings, per-product specifications, promotional vouchers, and store coordinates.
curl -X GET 'https://api.parse.bot/scraper/5c6f2345-187f-43bd-989b-7f261acb6c64/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 flanco-ro-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.
from parse_apis.flanco_ro_api import Flanco, Product, ProductDetail, Review, Store, Category, Subcategory
flanco = Flanco()
# Search for laptops
for product in flanco.products.search(query="laptop", limit=5):
print(product.name, product.price.current_price, product.availability)
# Get details for the first product found
detail = product.details.get()
print(detail.name, detail.seller, detail.availability)
for label, value in detail.specifications.items():
print(label, value)
# Check reviews for that product
for review in product.reviews.list(limit=3):
print(review.author, review.date, review.rating, review.content)
# Browse categories
for category in flanco.categories.list(limit=5):
print(category.name, category.url)
for sub in category.subcategories:
print(sub.name, sub.url)
# List products by category
for product in flanco.products.by_category(category_path="telefoane-tablete/smartphone", limit=10):
print(product.name, product.price.current_price)
# List all stores
for store in flanco.stores.list(limit=5):
print(store.title, store.city, store.region, store.phone)
Full-text search over Flanco's product catalog. Returns one page of matching products with names, current prices, and stock status. Pagination via the page param; each page returns up to ~25 items. Empty results are possible for obscure queries.
| Param | Type | Description |
|---|---|---|
| page | integer | Page number for pagination. |
| queryrequired | string | Search keyword (e.g. 'laptop', 'telefon samsung'). |
{
"type": "object",
"fields": {
"page": "string, current page number",
"query": "string, the search keyword used",
"products": "array of product objects with id, name, url, price, availability",
"total_count": "integer, number of products returned on this page"
},
"sample": {
"data": {
"page": "1",
"query": "laptop",
"products": [
{
"id": "933085",
"url": "https://www.flanco.ro/laptop-gaming-lenovo-loq-15irh8.html",
"name": "Laptop Gaming Lenovo LOQ 15IRH8",
"price": {
"current_price": "4.699,99lei"
},
"availability": "In stoc"
}
],
"total_count": 25
},
"status": "success"
}
}About the Flanco API
Product Search and Category Browsing
The search_products endpoint accepts a query string (e.g. 'laptop' or 'telefon samsung') and an optional page integer for pagination. Each response includes a products array where each item carries an id, name, url, price, and availability field, along with a total_count of results on the current page. For browsing by category, get_category_listings accepts a category_path such as 'telefoane-tablete/smartphone' — paths must match valid entries in the site's navigation tree. Invalid paths return an upstream_error with a 404 status; use get_categories first to retrieve the full hierarchical tree with valid url and name values and their nested subcategories.
Product Details and Reviews
get_product_details takes a full product URL or path segment and returns a structured object: price contains both current_price and an optional old_price for discounted items, specifications maps label strings to values (e.g. screen size, processor, RAM), and promotional_vouchers lists any active promo codes attached to the product. seller and availability fields indicate who is selling the item and whether it is currently in stock.
get_product_reviews takes a numeric product_id string — obtainable from search or category results — and returns an array of review objects, each with author, date, content, rating, and a verified_purchase boolean. The response also includes total_reviews and average_rating (which may be null if no reviews exist).
Store Locations
get_stores requires no inputs and returns the complete list of physical Flanco locations. Each store record includes city, region, address, phone, email, schedule (with possible HTML <br> line separators), and a coordinates array in [longitude, latitude] order — suitable for mapping or proximity filtering in downstream applications.
The Flanco API is a managed, monitored endpoint for flanco.ro — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when flanco.ro 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 flanco.ro 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 Flanco price drops on specific products by periodically calling
get_product_detailsand comparingcurrent_priceagainstold_price. - Build a Romanian electronics price comparison tool using
search_productsresults across multiple query terms. - Aggregate verified customer reviews and ratings from
get_product_reviewsto feed a product research dashboard. - Plot Flanco store locations on a map using the
coordinatesandaddressfields returned byget_stores. - Crawl the full product catalog by first fetching the category tree with
get_categories, then paginating through each path viaget_category_listings. - Monitor stock availability changes by polling
availabilityfields insearch_productsorget_product_detailsfor a watchlist of product IDs. - Extract product specifications from
get_product_detailsto populate a structured comparison table for a specific device category.
| 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 Flanco.ro have an official public developer API?+
What does `get_category_listings` return, and how do I find valid category paths?+
get_category_listings returns a paginated products array for a given category_path, where each product includes id, name, url, price, and availability. Valid paths must match existing site categories — passing an invalid path returns an upstream_error with a 404 status. Use get_categories first to retrieve all valid paths from the full category tree, including nested subcategories with their url fields.Does the API return product images?+
get_product_details and search/category endpoints return text fields such as name, price, specifications, and availability, but no image URLs are exposed in the current response schema. You can fork this API on Parse and revise it to add image URL extraction as an additional response field.Does the API cover product variants, such as different colors or storage sizes for the same model?+
id and url. Variant-level data (e.g. color or storage options) is not exposed as separate fields. You can fork the API on Parse and revise it to add variant enumeration for products that carry them.How does pagination work across endpoints?+
search_products and get_category_listings accept an optional page integer parameter. The response includes a page field confirming which page was returned. Neither endpoint currently returns a total page count or total product count across all pages — only total_count for the current page is available in search_products.