Hardverapro APIhardverapro.hu ↗
Access listings, prices, seller profiles, and category data from HardverApró, Hungary's largest tech marketplace, via a structured REST API.
What is the Hardverapro API?
The HardverApró API provides structured access to Hungary's largest hardware classifieds platform across 6 endpoints. Use search_listings to run full-text searches with price and category filters, get_listing_detail to retrieve complete product data including description, images, and seller info, or get_user_profile to fetch registration dates, ratings, and active listing counts for any public seller.
curl -X GET 'https://api.parse.bot/scraper/f3e0781b-7144-4a69-9881-e13f4dc826b1/search_listings?limit=10&query=RTX+4070&offset=0&category=hardver&max_price=500000&min_price=1000&subcategory=videokartya' \ -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 hardverapro-hu-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.hardverapró_api import HardverApro, Listing, ListingSummary, User, ListingNotFound
client = HardverApro()
# Search for GPU listings with a price filter
for summary in client.listingsummaries.search(query="RTX 4070", max_price=300000):
print(summary.title, summary.price, summary.user)
# Navigate from summary to full detail
detail = summary.details()
print(detail.title, detail.price, detail.seller_name, detail.category)
break
# Browse GPU category directly
for gpu in client.listingsummaries.gpus():
print(gpu.title, gpu.price, gpu.location)
break
# Fetch a specific listing by URL
listing = client.listings.get(url="https://hardverapro.hu/apro/rjnu_2/friss.html")
print(listing.title, listing.price, listing.seller_name, listing.seller_rating_summary)
# Get a user profile and browse their listings
user = client.users.get(username="C64")
print(user.username, user.display_name, user.regisztralt, user.rang)
for item in user.listings.list():
print(item.title, item.price, item.url)
Full-text search over HardverApró marketplace listings. Matches title text via the `query` parameter. Optionally scope to a category/subcategory and filter by price range. Returns up to `limit` listings starting at `offset`. Each listing carries title, URL, price, seller username, location, posting time, and detail tags. Paginates via integer offset (increments of up to `limit`).
| Param | Type | Description |
|---|---|---|
| limit | integer | Maximum number of listings to return |
| query | string | Search keyword to match against listing titles |
| offset | integer | Pagination offset (number of listings to skip) |
| category | string | Category slug: hardver, notebook, pc_szerver, mobil, szoftver_jatek, hazimozi_hifi, foto_video, egyeb |
| max_price | integer | Maximum price filter in HUF |
| min_price | integer | Minimum price filter in HUF |
| subcategory | string | Subcategory slug within the chosen category (e.g. videokartya, processzor, memoria, alaplap, ssd_hdd, monitor) |
{
"type": "object",
"fields": {
"query": "search keyword used or null",
"offset": "pagination offset used",
"category": "category slug used or null",
"listings": "array of listing summary objects with title, url, price, user, location, time, details",
"subcategory": "subcategory slug used or null"
},
"sample": {
"data": {
"query": "RTX 4070",
"offset": 0,
"category": null,
"listings": [
{
"url": "https://hardverapro.hu/apro/example/friss.html",
"time": "ma 10:00",
"user": "seller1",
"price": "219 990 Ft",
"title": "ASUS GeForce RTX 4070 SUPER 12GB",
"details": [],
"location": "Budapest"
}
],
"subcategory": null
},
"status": "success"
}
}About the Hardverapro API
Searching and Browsing Listings
search_listings accepts a query string matched against listing titles, optional min_price and max_price filters in HUF, and category scoping via category and subcategory slugs. Supported top-level categories include hardver, notebook, mobil, szoftver_jatek, hazimozi_hifi, foto_video, and egyeb. Subcategory slugs such as videokartya, processzor, memoria, alaplap, ssd_hdd, and monitor narrow results further. Responses include an array of listing objects carrying title, url, price, user, location, time, and details. list_category_listings mirrors this shape for pure category browsing without a keyword. Both endpoints paginate using integer offset and limit parameters.
Listing Detail and GPU Shortcut
get_listing_detail returns the full record for a single listing. The url input accepts either a full https://hardverapro.hu/apro/... URL or a bare slug like rjnu_2. Response fields include uid, price (integer HUF when parseable, otherwise a string), description, images (array of URLs), city, region, category (full path string), and seller_name. list_gpu_listings is a dedicated shortcut for the hardver/videokartya subcategory, returning the standard listing shape with a single offset parameter — useful for monitoring the GPU secondhand market without constructing category parameters manually.
Seller Profiles and User Listings
get_user_profile returns public profile data for any username: rang (site rank), regisztralt (registration date and tenure), utoljara_belepve (last login timestamp), ertekelesek (ratings summary), hirdetesek (active listings count), and display_name. get_user_listings retrieves all active ads posted by a given user, paginated by offset, and returns the same listing objects as the search endpoints. These two endpoints together let you build seller reliability checks or monitor specific traders' inventory changes over time.
The Hardverapro API is a managed, monitored endpoint for hardverapro.hu — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when hardverapro.hu 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 hardverapro.hu 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 GPU secondhand prices in Hungary using
list_gpu_listingsand recording thepricefield over time. - Build a price alert tool that polls
search_listingswithmin_price/max_pricefilters for specific hardware keywords. - Aggregate seller trust signals by combining
get_user_profileratings with their listing history fromget_user_listings. - Index full listing descriptions and images for a hardware comparison or aggregator site using
get_listing_detail. - Monitor new listings in a specific subcategory (e.g.
processzororssd_hdd) by pollinglist_category_listingswith a rollingoffset. - Analyze regional distribution of tech listings by collecting the
cityandregionfields fromget_listing_detailresponses. - Assess seller activity patterns by comparing
regisztralt,utoljara_belepve, andhirdetesekfromget_user_profile.
| 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 HardverApró have an official developer API?+
What does `get_listing_detail` return that the listing summary endpoints don't?+
get_listing_detail returns fields not present in listing summaries: the full description text, an images array of image URLs, the integer uid, the canonical url, a full category path string, and separate city and region fields. Summary listings from search or category endpoints carry only title, url, price, user, location, time, and details.Can I filter `search_listings` by both category and price at the same time?+
search_listings accepts category, subcategory, min_price, and max_price as independent optional parameters that can all be combined in a single request alongside the query keyword. Results are paginated using offset and limit.Does the API expose private messaging, bidding, or negotiation features?+
Is there a way to retrieve historical or sold listings?+
search_listings, list_category_listings, list_gpu_listings, and get_user_listings. Closed or sold listings are not included in responses. You can fork this API on Parse and revise it to add a historical or sold-listings endpoint if that data is publicly accessible on the site.