hardverapro.hu APIhardverapro.hu ↗
Access listings, categories, GPU inventory, seller profiles, and listing details from HardverApró, Hungary's largest used hardware marketplace.
curl -X GET 'https://api.parse.bot/scraper/f3e0781b-7144-4a69-9881-e13f4dc826b1/search_listings?limit=10&query=RTX' \ -H 'X-API-Key: $PARSE_API_KEY'
Search for listings on HardverApró with optional filters.
| Param | Type | Description |
|---|---|---|
| limit | integer | Maximum number of results to return |
| query | string | Search keyword |
| offset | integer | Pagination offset |
| category | string | Category slug (e.g., 'hardver', 'notebook') |
| max_price | integer | Maximum price in HUF |
| min_price | integer | Minimum price in HUF |
| subcategory | string | Subcategory slug (e.g., 'videokartya', 'processzor') |
{
"type": "object",
"fields": {
"query": "string",
"offset": "integer",
"listings": "array of objects (title, url, price, user, location, time, details)"
},
"sample": {
"data": {
"query": "RTX",
"offset": 0,
"category": null,
"listings": [
{
"url": "https://hardverapro.hu/apro/bluesummers_bazarja/friss.html",
"time": "Előresorolva",
"user": "Bluesummers",
"price": "12 300 Ft",
"title": "Licencek + laptopok + dokkolók",
"details": [],
"location": "Külföld"
},
{
"url": "https://hardverapro.hu/apro/uj_es_hasznalt_laptopok_uzletitol_a_gamerig_legjob_2/friss.html",
"time": "Előresorolva",
"user": "donpadre",
"price": "99 900 Ft",
"title": "Új és használt laptopok , üzletitől a gamerig , kedvező áron. Garanciával !",
"details": [],
"location": "Budapest"
},
{
"url": "https://hardverapro.hu/apro/bluesummers_bazarja_3/friss.html",
"time": "Előresorolva",
"user": "Bluesummers",
"price": "100 Ft",
"title": "LENOVO GAMER BAZÁR - új lista (2026.02.23)",
"details": [],
"location": "Külföld"
}
],
"subcategory": null
},
"status": "success"
}
}About the hardverapro.hu API
The HardverApró API exposes 6 endpoints covering listings, categories, and seller data from Hungary's primary tech classifieds site. You can search listings with keyword, price range, and category filters via search_listings, pull full listing detail including images and condition via get_listing_detail, or retrieve a seller's public profile and active ads using get_user_profile and get_user_listings.
Searching and Browsing Listings
The search_listings endpoint accepts a query string alongside optional min_price and max_price filters (both in HUF), a category slug such as hardver or notebook, and a subcategory slug like videokartya or processzor. Results are paginated using limit and offset parameters and each entry in the listings array includes the title, URL, price, seller username, location, listing time, and a details object. The list_category_listings endpoint covers the same category/subcategory slug system and returns a listings array in the same shape, useful when you want to enumerate an entire category without a keyword filter.
Listing Detail and GPU Shortcut
get_listing_detail takes a full listing URL or slug and returns structured fields: uid, title, price, city, region, allapot (condition), szandek (intent — buy/sell/exchange), category, and an images array of URLs. This is the only endpoint that surfaces condition and intent metadata. list_gpu_listings is a dedicated shortcut for the videokartya (GPU) subcategory — it accepts only an offset parameter and returns the same listings array format, saving you the need to supply category and subcategory slugs when GPU data is all you need.
Seller and User Data
get_user_profile accepts a username and returns display_name, regisztralt (registration date), hirdetesek (listing count), and ertekelesek (review/rating count). To retrieve the actual ads a seller has posted, get_user_listings takes the same username with an optional offset and returns a paginated listings array. Together these two endpoints let you build seller reputation checks or monitor a specific account's inventory over time.
- Monitor used GPU prices in Hungary by polling
list_gpu_listingsand tracking price changes over time. - Build a price-comparison tool for Hungarian hardware buyers using
search_listingswithmin_priceandmax_pricefilters. - Check seller credibility before a transaction by fetching
ertekelesek(review count) andregisztralt(registration date) fromget_user_profile. - Aggregate all active listings from a specific seller using
get_user_listingsfor inventory tracking or reseller research. - Extract listing condition (
allapot) and intent (szandek) data fromget_listing_detailto filter for new-only or sell-only ads. - Enumerate every listing in a category like
mobilornotebookusinglist_category_listingswith pagination for market analysis. - Feed structured HardverApró listing data (title, price, images, city) into a deal-alert or notification service.
| 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 HardverApró have an official public developer API?+
What does `get_listing_detail` return that the listing search endpoints don't?+
get_listing_detail returns fields not present in search or category results: allapot (condition, e.g. used/new), szandek (intent — sell, buy, or swap), a full images array, and the region field alongside city. The listing array endpoints return a summary object per item without these fields.Are private or expired listings accessible through this API?+
offset is available on all listing endpoints to iterate through large result sets.Does the API cover seller ratings or individual review text?+
get_user_profile returns ertekelesek, which is the aggregate review count for a user. Individual review text, rating breakdowns, or per-transaction feedback are not currently exposed. You can fork this API on Parse and revise it to add an endpoint targeting per-review detail if your use case requires it.Can I filter listings by region or city?+
search_listings and list_category_listings do not currently accept a location filter as an input parameter. The city and region fields are returned in get_listing_detail responses, but filtering by geography at query time is not supported. You can fork this API on Parse and revise it to add location-based filtering if needed.