Aukro Listing Lookup: Czech Auctions and Fixed-Price Items

Search Aukro (aukro.cz) by keyword and get one clean row per auction or fixed-price listing: current bid, buy-now price, price with shipping, condition, category, end time and a link. Turn on monitoring mode and run it on a schedule to get only the listings that are new since your last run, charged per listing and free on a quiet day.

Who uses it: resellers and flippers watching the Czech second-hand market for under-priced items, collectors tracking a model or a brand, and price researchers comparing what Czech buyers pay for used electronics, cars parts, toys or antiques.

How to use

1. In the Apify Console. Open the actor page and click Start — the queries field is already pre-filled with a working example. Results land in the run's dataset as soon as each item is found.
2. Via the API. Call it directly with a POST request — no Console needed once you have an API token:

   curl "https://api.apify.com/v2/acts/accountable_eel~aukro-listing-lookup/run-sync-get-dataset-items?token=<YOUR_TOKEN>" \
     -X POST \
     -H "Content-Type: application/json" \
     -d '{"queries":["samsung galaxy"]}'
   

3. On a schedule. Save this actor as an Apify Task with the input you want, then add a Schedule (hourly, daily, weekly) so it runs on its own — no server of your own required.

Input

{
  "queries": [
    "samsung galaxy"
  ]
}

One search phrase per line, exactly as you would type it into the Aukro search box (Czech or any language the sellers used), for example samsung galaxy. All lines run in one combined search and the run cap is shared between them. Accepted formats: samsung galaxy, nintendo switch, starožitné hodinky.

All search lines run as one combined search and the listing cap is shared between them. Optional filters (listing type, minimum and maximum current price in CZK) run after the fetch. Aukro sometimes treats a very broad term (for example a bare brand name) as a whole category page and returns no listings for it: use a more specific phrase such as samsung galaxy or iphone 13 128gb.

Output

One row per listing, for example:

query	found	status	searchSummary	listingCount	truncated	monitorStatus	listings	itemId	title	listingType	currentPriceCzk	buyNowPriceCzk	priceWithShippingCzk	retailPriceCzk	quantity	condition	attributes	category	categoryPath	itemLocation	freeShipping	personalPickup	watchersCount	sellerType	sellerCountry	sellerFeedbackCount	sellerPositiveFeedbackPercent	startsAt	endsAt	imageUrl	listingUrl	searchQuery	isNew	firstSeenAt	scrapedAt
samsung galaxy	true	OK					<all listings (full list)>				<current price (czk)>	<buy-now price (czk)>	<price with cheapest shipping (czk)>	<retail price shown by seller (czk)>						<item location (town)>							<seller positive feedback (%)>						<is this listing new?>		1970-01-01T00:00:00.000Z

currentPriceCzk is the current bid for an auction and the asking price for a fixed-price listing. buyNowPriceCzk, retailPriceCzk and any other missing value come back as null, never 0. A search with no matching listings comes back as one row with "found": false and is never charged. The seller's name, login and contact details are not returned: only the seller type (private or business), country and feedback numbers.

Pricing

Pay-per-event: you are billed per listing returned. A search with no results and a monitoring run with nothing new are never charged.

Example runs

Paste any of these into the Input tab and press Start. All three return rows with no key, no token and no account of your own beyond an Apify login.

Used Samsung phones, any listing type. The default shape.

{
  "queries": ["samsung galaxy"],
  "maxResults": 60
}

Auctions only for a console, under 4,000 CZK.

{
  "queries": ["nintendo switch"],
  "listingType": "auction",
  "maxPriceCzk": 4000
}

New-listing alert for a collectible, with monitoring on. The first run stores a baseline; later runs return and bill only listings not seen before.

{
  "queries": ["starožitné hodinky"],
  "onlyNewSinceLastRun": true,
  "deltaName": "watches-watch"
}

Monitoring compares against the first results Aukro ranks for your phrase (up to the per-run cap), so use a specific phrase and run it often enough that new listings stay inside that window.

Use it from Clay, n8n, Make, or an AI agent

This actor runs synchronously over plain HTTP — call it directly from a script, a workflow tool, or an AI agent, no Apify Console needed once you have an API token.

curl "https://api.apify.com/v2/acts/accountable_eel~aukro-listing-lookup/run-sync-get-dataset-items?token=<YOUR_TOKEN>" \
  -X POST \
  -H "Content-Type: application/json" \
  -d '{"queries":["samsung galaxy"]}'

n8n. Add an HTTP Request node: Method POST, URL https://api.apify.com/v2/acts/accountable_eel~aukro-listing-lookup/run-sync-get-dataset-items?token=<YOUR_TOKEN>, Body Content Type JSON, JSON Body {"queries":["samsung galaxy"]} (swap in an expression from an earlier node for a real value).

Clay. Add an "HTTP API" column: Method POST, URL https://api.apify.com/v2/acts/accountable_eel~aukro-listing-lookup/run-sync-get-dataset-items?token=<YOUR_TOKEN>, Body {"queries":["{{search}}"]}, mapping the row's search into the queries array.

MCP. In Claude, Cursor, or any MCP client with the Apify MCP server, ask for "aukro scraper" — the agent will find and run this actor.