# Tradera Sold Prices & New Listing Alerts (`accountable_eel/tradera-sold-lookup`) Actor Tradera sold prices: ended auctions with final price and bid count, plus live and unsold listings, one row per listing. Optional price summary per search. Monitor a search and get new-listing or price-below alerts in Slack, Discord or Telegram. No login or key; empty searches are free. - **URL**: https://apify.com/accountable_eel/tradera-sold-lookup.md - **Developed by:** [Adriana Voss](https://apify.com/accountable_eel) (community) - **Categories:** E-commerce, Automation - **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks - **User rating**: No ratings yet ## Pricing from $0.75 / 1,000 listing returneds This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events. Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have. Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event ## What's an Apify Actor? An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes. In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours, and optionally produces a well-defined JSON output, datasets with results, or files in key-value store. In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server. Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md. ## How to integrate an Actor? If asked about integration, you help developers integrate Actors into their projects. You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready. Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run. For examples already wired to this Actor's own input schema, see the [API](#api) section below. Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`). # README ## Tradera Sold Prices & New Listing Alerts Type a search, get what Swedish buyers actually paid. The actor reads **Tradera**'s search pages and returns one row per listing: the **final sold price in SEK**, the **number of bids**, the end date, the listing type, condition, shipping and seller handle. Switch on the summary and each search also gets one extra row with the **median, quartiles, lowest and highest price**. Switch on monitoring and it flags **new listings** or listings **priced below your limit** and posts them to Slack, Discord or Telegram. It covers sold, unsold and live listings, so the same actor answers "what does this sell for?", "what did not sell?" and "what was just listed?". ### Who uses this - **Resellers and flippers** who price an item from real sold auctions before they buy or list it. - **Bargain hunters and deal channels** who want a message the moment a matching item is listed or drops under their limit. - **Collectors, dealers and appraisers** who track what a model, set or edition fetches over time, in a sheet or an n8n / Make / Clay workflow. ### Try it in 30 seconds Press **Start** with the pre-filled input. It reads the sold `iphone 13` listings on Tradera and returns 50 rows plus one price summary: ```json { "searches": ["iphone 13"], "mode": "sold", "maxItems": 50, "includeCompsSummary": true } ``` Write your own lines, one search per line: ```text iphone 13 lego star wars 75192 https://www.tradera.com/search?q=iphone+13 ``` A pasted Tradera search link is read for its search words only; price, category and dates come from the settings. ### What you get One **item row** per listing: | Field | Meaning | | --- | --- | | `itemId`, `url`, `title` | Tradera's item number, the listing link and the seller's title. | | `priceSek` | Sold: the **final price paid** (a buy-now listing sold through an accepted offer shows the accepted price). Unsold and live: the last or current price. | | `bids`, `itemType` | Number of bids; `auction`, `auction-buy-now`, `buy-now` or `shop-item`. | | `listingStatus` | `sold`, `unsold` or `live`. | | `startDate`, `endDate` | When the listing started and ended or ends (UTC). | | `condition`, `shippingSek`, `categoryId` | Condition in Tradera's wording, the lowest shipping price (0 = free, empty = pick-up only), and the category number. | | `sellerAlias`, `sellerIsCompany` | The seller's public handle, and whether the seller is a company. | | `changeType`, `previousPriceSek`, `alertType` | Monitoring fields (empty unless you turn monitoring on). | One **summary row** per search, when you ask for it: `count`, `soldCount`, `medianSek`, `p25Sek`, `p75Sek`, `lowSek`, `highSek`, `medianBids`, `newestEndDate`, and `priceBasis` (`sold-price` in sold mode, `last-price` for unsold, `current-price` for live, so a live summary is never mistaken for sale prices). It is worked out from the listing rows you receive, so a price filter or keyword filter changes it. Settings, each one verified to change the result: `mode` (sold, live, unsold), `categoryId`, `minPrice` / `maxPrice`, `sortBy` (best match or newest listed), `maxItems`. Applied by the actor after reading: `endedAfter`, the final-price check on `minPrice` / `maxPrice`, the keyword filters and the `columns` choice. ### Example: sold prices, a summary and a Discord alert Daily run over live listings that returns only what is new or changed, and posts a listing to a Discord channel the first time it shows up at 1,500 SEK or less: ```json { "searches": ["iphone 13"], "mode": "live", "maxItems": 100, "maxPrice": 3000, "deltaMode": true, "deltaName": "iphone-13-live", "skipFirstRun": true, "alertOnChangeOnly": true, "alertOn": "price-below", "alertBelowSek": 1500, "notifyUrl": "" } ``` And the sold-price version, a one-off price check you can paste into a sheet: ```json { "searches": ["lego star wars 75192"], "mode": "sold", "maxItems": 200, "endedAfter": "2026-08-01", "includeCompsSummary": true } ``` ### Monitoring: a new-listing alert in three steps 1. **Turn on monitoring and name the watchlist.** Tick **Remember listings between runs**, type a **Watchlist name**, tick **Only return rows that changed** (a repeat run writes no row and costs nothing) and **Seed silently** (the first run only records what is there, so alerts start from the second run). 2. **Schedule it.** Save the input as an Apify Task and add a daily or hourly Schedule. Each run compares every listing with the previous run of the same watchlist and search: `changeType` is `new`, `price-drop`, `price-rise` or `unchanged`. In **live** mode, newest listings come first, so a short `maxItems` is enough to catch everything new. In **sold** mode, "new" means newly sold. 3. **Send it somewhere.** Paste a Slack or Discord webhook (or a Telegram bot link) into **Send alerts to**. Each `new-listing` or `price-below` row arrives as one message with title, price, bids, end date and the Tradera link. For n8n or Make, leave the format on JSON, or read the dataset rows where `alertType` is set. Alerts are only sent for rows that were actually billed, messages are never billed, and a failed message never fails the run (the row's `notifyErrors` says why). A run posts at most 20 messages by default, then one "more alerts" message. ### Limits, stated plainly - **Sweden, in SEK.** Tradera's Swedish site and prices. Other currencies are not converted. - **Ended auctions as the search shows them.** The sold list is Tradera's own "Sålda" filter. The actor does not open individual listings, so there are no descriptions, photos or bid histories, and no bidder information of any kind. - **Up to 10,000 listings per search, 25 pages read.** Tradera shows at most 125 pages of 80 listings. This actor reads at most 25 pages (2,000 listings) per search line; a strict date or price filter that rejects most of a long list can use up the pages before `maxItems` is reached. - **Best match is not stable.** Tradera re-ranks between page requests, so a long best-match list can repeat or skip a listing; repeats are removed. Use `sortBy: newest` when completeness matters. - **Price filters follow the final price.** Tradera filters on the listed price, the actor then checks the final price too, so a sold row satisfies both. - **Date filters are UTC.** `endedAfter` compares the end date in UTC; Swedish time is 1 to 2 hours ahead. - **Searches only.** One request a second, search pages only; nothing is logged in, bought, bid on or messaged. - **Misses are free.** Not found, blocked, challenge page, layout change: nothing is charged. ### How to use 1. **In the Apify Console.** Open the actor page and click **Start** — the `searches` 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: ```bash curl "https://api.apify.com/v2/acts/accountable_eel~tradera-sold-lookup/run-sync-get-dataset-items?token=" \ -X POST \ -H "Content-Type: application/json" \ -d '{"searches":["iphone 13"]}' ``` 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 ```json { "searches": [ "iphone 13" ] } ``` One search per line: keywords such as iphone 13, or a pasted tradera.com search link (only its search words are used; set price, category and dates below). Each search returns one row per listing. Accepted formats: iphone 13, lego star wars 75192, https://www.tradera.com/search?q=iphone+13. ### Output One row per listing, for example: | query | found | status | rowType | itemId | url | title | categoryId | priceSek | buyNowSek | bids | startDate | endDate | itemType | listingStatus | condition | shippingSek | sellerAlias | sellerIsCompany | checkedAt | changeType | previousPriceSek | alertType | notifyErrors | priceBasis | count | soldCount | medianSek | p25Sek | p75Sek | lowSek | highSek | medianBids | newestEndDate | scrapedAt | | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | | iphone 13 | true | OK | | | | | <category id> | \<price (sek)> | \<buy-now price (sek)> | <bids> | <start date> | <end date> | <listing type> | <listing status> | <condition> | \<shipping from (sek)> | <seller handle> | <company seller> | <checked at> | <change since last run> | \<previous price (sek)> | <alert> | <alert delivery errors> | \<summary: price basis> | \<summary: listings> | \<summary: sold> | \<summary: median (sek)> | \<summary: 25th percentile (sek)> | \<summary: 75th percentile (sek)> | \<summary: lowest (sek)> | \<summary: highest (sek)> | \<summary: median bids> | \<summary: newest end date> | 1970-01-01T00:00:00.000Z | A search that finds nothing comes back as one row with `"found": false` and is never charged. ### Pricing Pay-per-event. A flat per-run fee covers session/proxy warmup; you're billed per item only when data is actually found and returned — see `.actor/pay_per_event.json` for exact prices. A miss is never charged. ### 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. ```bash curl "https://api.apify.com/v2/acts/accountable_eel~tradera-sold-lookup/run-sync-get-dataset-items?token=<YOUR_TOKEN>" \ -X POST \ -H "Content-Type: application/json" \ -d '{"searches":["iphone 13"]}' ``` **n8n.** Add an HTTP Request node: Method `POST`, URL `https://api.apify.com/v2/acts/accountable_eel~tradera-sold-lookup/run-sync-get-dataset-items?token=<YOUR_TOKEN>`, Body Content Type `JSON`, JSON Body `{"searches":["iphone 13"]}` (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~tradera-sold-lookup/run-sync-get-dataset-items?token=<YOUR_TOKEN>`, Body `{"searches":["{{search}}"]}`, mapping the row's search into the `searches` array. **MCP.** In Claude, Cursor, or any MCP client with the Apify MCP server, ask for "Tradera Sold Prices & New Listing Alerts | Apify" — the agent will find and run this actor. # Actor input Schema ## `searches` (type: `array`): One search per line: keywords such as iphone 13, or a pasted tradera.com search link (only its search words are used; set price, category and dates below). Each search returns one row per listing. Accepted formats: iphone 13, lego star wars 75192, https://www.tradera.com/search?q=iphone+13. You're only charged for the ones we actually find — a miss costs nothing. ## `mode` (type: `string`): Sold: ended auctions that sold, with the final price. Live: listings that are for sale now, newest first. Unsold: ended auctions nobody bought. ## `maxItems` (type: `integer`): Most listings returned for each search line (80 per page, at most 25 pages read). Local filters below are applied while reading, so this counts listings that passed them. ## `categoryId` (type: `integer`): Tradera's category number, the last number in a category link such as tradera.com/category/2601 (Mobiltelefoner). Leave empty to search every category. ## `minPrice` (type: `integer`): Optional. Keeps listings priced at or above this. Sent to Tradera (which reads the listed price) and then enforced on the final price, so a sold row must satisfy both. ## `maxPrice` (type: `integer`): Optional. Keeps listings priced at or below this. Sent to Tradera and then enforced on the final price, so a sold row must satisfy both. ## `endedAfter` (type: `string`): Optional, sold and unsold searches only. Keeps listings whose end date (UTC) is on or after this date. Applied after reading, so a long ago date costs more pages, not more money; the run stops after 25 pages per search. ## `sortBy` (type: `string`): Auto reads live searches newest first and sold or unsold searches in Tradera's best-match order. Newest listed puts the most recently listed items first, whatever the mode. ## `includeCompsSummary` (type: `boolean`): Adds one extra row after each search: how many listings, how many sold, median, 25th and 75th percentile, lowest, highest, median bids and the newest end date, worked out from the listings returned. Billed as one summary per search that returned listings. ## `deltaMode` (type: `boolean`): Turns the actor into a monitor. Each run compares every listing with what the previous run of the same watchlist saw and fills in the change, previous price and alert columns. Schedule it daily and combine with the options below. ## `deltaName` (type: `string`): Leave empty and one is derived from the mode and price settings. Type your own name to keep one memory across changes, or to run several independent watchlists. ## `alertOn` (type: `string`): New listing: a listing not seen on the previous run (in Sold mode, a newly sold item). Price below: a listing at or under the limit below that was not already under it. Both: either. ## `alertBelowSek` (type: `integer`): Used by "Price below my limit". Leave empty and price alerts are off. ## `alertOnChangeOnly` (type: `boolean`): With monitoring on, a listing already seen at the same price writes no row and is not billed. New listings, price changes and alerts are returned. ## `skipFirstRun` (type: `boolean`): The first run of a search has nothing to compare with, so every listing is new. Turn this on to remember them without returning or billing them, so alerts start from the second run. ## `notifyUrl` (type: `string`): Optional. After a listing is billed, each alert row is posted here as one message with title, price, bids, end date and the Tradera link. Discord or Slack: paste the channel's webhook URL. Telegram: https://api.telegram.org/bot<token>/sendMessage?chat_id=<chat id>. Any other URL receives JSON. Messages are free, and a failed message never fails the run (the row's notifyErrors says why). Stored encrypted, never logged or written to the results. ## `notifyFormat` (type: `string`): Leave on 'Detect from the link': discord.com links get Discord messages, hooks.slack.com Slack, api.telegram.org Telegram, anything else JSON. Pick one only to override that. ## `maxNotificationsPerRun` (type: `integer`): Alerts above this are still in the results; one "more alerts" message is sent instead. 0 sends only that message. ## `testRun` (type: `boolean`): Turn this on to test your input on a small sample before running the full list. Turn it off to process everything. ## `onlyFound` (type: `boolean`): Only keep rows where something was actually found. Misses are always free, whether or not you show them here. ## `includeKeywords` (type: `array`): Optional, case-insensitive. Keeps only listings whose title, condition, seller or link contains at least one of these words. Applied after the listings are read, so you can get fewer rows than the limit above. ## `excludeKeywords` (type: `array`): Optional, case-insensitive. Drops any listing whose title, condition, seller or link contains one of these words. Applied after the listings are read. ## `maxResults` (type: `integer`): Optional. Stop the run once this many results have been found — useful for a quick, cheap sample. Leave blank for no limit. ## `columns` (type: `array`): Choose which pieces of information to include in each result row. All are included by default. ## `expandRows` (type: `boolean`): Always on: every listing is its own row. ## `maxConcurrency` (type: `integer`): Parallel requests. Keep conservative — this target has no browser fallback, so getting blocked costs more than slow-and-steady. ## `proxyConfiguration` (type: `object`): Apify Proxy config. Residential recommended for anti-bot-sensitive targets. ## Actor input object example ```json { "searches": [ "iphone 13" ], "mode": "sold", "maxItems": 50, "endedAfter": "", "sortBy": "auto", "includeCompsSummary": true, "deltaMode": false, "deltaName": "", "alertOn": "new-listing", "alertOnChangeOnly": false, "skipFirstRun": false, "notifyFormat": "auto", "maxNotificationsPerRun": 20, "testRun": false, "onlyFound": false, "includeKeywords": [], "excludeKeywords": [], "columns": [ "rowType", "itemId", "url", "title", "categoryId", "priceSek", "buyNowSek", "bids", "startDate", "endDate", "itemType", "listingStatus", "condition", "shippingSek", "sellerAlias", "sellerIsCompany", "checkedAt", "changeType", "previousPriceSek", "alertType", "notifyErrors", "priceBasis", "count", "soldCount", "medianSek", "p25Sek", "p75Sek", "lowSek", "highSek", "medianBids", "newestEndDate" ], "expandRows": true, "maxConcurrency": 1, "proxyConfiguration": { "useApifyProxy": true } } ``` # Actor output Schema ## `results` (type: `string`): No description # API You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup. ## JavaScript example ```javascript import { ApifyClient } from 'apify-client'; // Initialize the ApifyClient with your Apify API token // Replace the '<YOUR_API_TOKEN>' with your token const client = new ApifyClient({ token: '<YOUR_API_TOKEN>', }); // Prepare Actor input const input = { "searches": [ "iphone 13" ], "includeCompsSummary": true, "includeKeywords": [], "excludeKeywords": [] }; // Run the Actor and wait for it to finish const run = await client.actor("accountable_eel/tradera-sold-lookup").call(input); // Fetch and print Actor results from the run's dataset (if any) console.log('Results from dataset'); console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`); const { items } = await client.dataset(run.defaultDatasetId).listItems(); items.forEach((item) => { console.dir(item); }); // 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs ``` ## Python example ```python from apify_client import ApifyClient # Initialize the ApifyClient with your Apify API token # Replace '<YOUR_API_TOKEN>' with your token. client = ApifyClient("<YOUR_API_TOKEN>") # Prepare the Actor input run_input = { "searches": ["iphone 13"], "includeCompsSummary": True, "includeKeywords": [], "excludeKeywords": [], } # Run the Actor and wait for it to finish run = client.actor("accountable_eel/tradera-sold-lookup").call(run_input=run_input) # Fetch and print Actor results from the run's dataset (if there are any) print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}") for item in client.dataset(run.default_dataset_id).iterate_items(): print(item) # 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start ``` ## CLI example ```bash echo '{ "searches": [ "iphone 13" ], "includeCompsSummary": true, "includeKeywords": [], "excludeKeywords": [] }' | apify call accountable_eel/tradera-sold-lookup --silent --output-dataset ``` ## MCP server setup ```json { "mcpServers": { "apify": { "type": "http", "url": "https://mcp.apify.com/?tools=fetch-actor-details,accountable_eel/tradera-sold-lookup" } } } ``` The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations). ## OpenAPI specification Download the OpenAPI definition: https://api.apify.com/v2/actors/brJ3DrWzNk9tCQ6u5/builds/4VkJPmS0dPiIeBTGj/openapi.json