# Bring a Trailer Sold Prices & Comps API (`accountable_eel/bring-a-trailer-sold-lookup`) Actor Bring a Trailer sold prices: one row per sold lot (title, year, make, model, final price, end date, no-reserve) for any search, plus an optional comps summary with median, quartiles, low, high and 90-day trend. New-result alerts to Slack, Discord or Telegram. Searches that find nothing are free. - **URL**: https://apify.com/accountable_eel/bring-a-trailer-sold-lookup.md - **Developed by:** [Adriana Voss](https://apify.com/accountable_eel) (community) - **Categories:** Automation, E-commerce - **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks - **User rating**: No ratings yet ## Pricing from $4.98 / 1,000 auction lot 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 ## Bring a Trailer Sold Prices & Comps API Sold prices from Bring a Trailer, as rows you can sort, chart and price a buy against. Type a make and model as you would in the site's search box and get one row per finished auction: the title, year, make, model, what it sold for, the end date, whether it ran with no reserve and a link to the lot. Add the optional comps summary and every search also comes back as one row of median, quartiles, low, high and the 90-day trend. Schedule it with the monitoring options and new results are posted to Slack, Discord or Telegram. It reads the same public results data the Bring a Trailer results page shows. No login, no key, no seller or bidder data. ### 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~bring-a-trailer-sold-lookup/run-sync-get-dataset-items?token=" \ -X POST \ -H "Content-Type: application/json" \ -d '{"searches":["porsche 911"]}' ``` 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": [ "porsche 911" ] } ``` One search per line: a make and model, or any words you would type into the Bring a Trailer search box, for example porsche 911 or land rover defender 90. Accepted formats: porsche 911, land rover defender 90, bmw e30 m3. ### Output One row per sold lot, and (when you ask for it) one comps summary row per search. A single lot row: ```json { "query": "porsche 911", "found": true, "status": "OK", "rowType": "lot", "title": "42k-Mile 1997 Porsche 911 Carrera Targa", "year": 1997, "make": "Porsche", "model": "911 Carrera Targa", "result": "sold", "currency": "USD", "finalPrice": 88000, "finalPriceUsd": 88000, "endDate": "2026-10-19", "noReserve": false, "location": "US", "lotUrl": "https://bringatrailer.com/listing/…" } ``` The table below shows every column the dataset can carry: | query | found | status | rowType | search | title | year | make | model | result | currency | finalPrice | finalPriceUsd | highBidUsd | endDate | endedAt | noReserve | location | lotUrl | lotId | checkedAt | changeType | alertMatch | matchesOnSite | count | soldCount | medianUsd | p25Usd | p75Usd | lowUsd | highUsd | last90dCount | last90dMedianUsd | prior90dCount | prior90dMedianUsd | trendPct | newestEndDate | oldestEndDate | scrapedAt | | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | | porsche 911 | true | OK | | | | | | | | | | \ | \ | | | | | | | | | | | | | \ | <25th percentile (usd)> | <75th percentile (usd)> | \ | \ | \ | \ | \ | \ | \ | | | 1970-01-01T00:00:00.000Z | A search that finds nothing comes back as a row with `"found": false` and is never charged. ### Example: a search with a comps summary ```json { "searches": ["porsche 911", "land rover defender"], "maxLots": 300, "includeCompsSummary": true, "yearFrom": 1990 } ``` Each search returns its sold lots, newest first, and then one `comps-summary` row: ```json { "rowType": "comps-summary", "search": "land rover defender", "matchesOnSite": 1350, "count": 300, "soldCount": 289, "medianUsd": 46000, "p25Usd": 34500, "p75Usd": 61000, "lowUsd": 14250, "highUsd": 187000, "last90dMedianUsd": 48500, "prior90dMedianUsd": 44000, "trendPct": 10.2 } ``` (The numbers above only show the shape of the row.) The summary is plain arithmetic over the sold lots the run read, with no extra requests, so `count` and `oldestEndDate` tell you how far back it reaches. A trend needs lots from both the last 90 days and the 91 to 180 days before; if the run did not read far enough back, those medians and the trend are empty. ### Monitoring: new results as alerts Turn on **Track new results across runs**, give the watchlist a name and schedule the run daily. Each lot is marked `new` the first time that search returns it and `seen` after. Choose what counts as an alert: every new result, or a new sold lot at or above, or at or below, a price. **Only return new alerts** keeps just those rows, and **Send alerts to** posts each one to a Discord or Slack webhook, a Telegram bot or any URL as JSON. The first run of a search has nothing to compare with, so turn on **Seed silently** to remember it without returning or billing it. ### Fields - **result**: `sold`, `bid-to` (bidding stopped below the reserve) or `withdrawn`. Only with **Sold lots only** switched off do the last two appear. - **finalPrice / finalPriceUsd**: the "Sold for" figure Bring a Trailer prints. `finalPriceUsd` is filled when that figure is in US dollars. - **highBidUsd**: for a lot that did not sell, the last bid shown. - **year, make, model**: read out of the title. The site's own results list carries no separate year, make or model, so the make is matched against a list of marques and the model is what follows it. A title that names a make we do not know leaves make and model empty. - **endDate**: the end date as the site prints it (a US date). **endedAt** is the exact timestamp. - **location**: the lot's two-letter country code. The results list does not carry a US state. ### Limits - **Sold results as Bring a Trailer shows them.** Prices are the printed "Sold for" figures, not a valuation, and not adjusted for condition, mileage or fees. - **USD only.** A few lots sell in pounds or euros. They are returned with their own `currency` and `finalPrice`, no `finalPriceUsd`, and they are left out of the comps arithmetic. There is no currency conversion. - **No seller or bidder data.** No names, bidder lists, comments or bid counts: the results list does not carry bid or comment counts, so they are not columns. - **Parts and memorabilia.** Bring a Trailer also sells manuals, parts and signs. **Vehicles only** (on by default) drops lots whose title carries no model year; turn it off to keep them. - **One request per second.** A page holds 36 lots, so reading 300 lots takes about 10 seconds. At most 2,000 lots per search and 50 searches per run. - **A block or a changed page costs nothing.** Searches that find nothing, a bot check or a changed response come back as a free miss row that says why. ### 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~bring-a-trailer-sold-lookup/run-sync-get-dataset-items?token=" \ -X POST \ -H "Content-Type: application/json" \ -d '{"searches":["porsche 911"]}' ``` **n8n.** Add an HTTP Request node: Method `POST`, URL `https://api.apify.com/v2/acts/accountable_eel~bring-a-trailer-sold-lookup/run-sync-get-dataset-items?token=`, Body Content Type `JSON`, JSON Body `{"searches":["porsche 911"]}` (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~bring-a-trailer-sold-lookup/run-sync-get-dataset-items?token=`, Body `{"searches":["{{sold lot}}"]}`, mapping the row's sold lot into the `searches` array. **MCP.** In Claude, Cursor, or any MCP client with the Apify MCP server, ask for "Bring a Trailer Sold Prices & Comps API | Apify" — the agent will find and run this actor. # Actor input Schema ## `searches` (type: `array`): One search per line: a make and model, or any words you would type into the Bring a Trailer search box, for example porsche 911 or land rover defender 90. Accepted formats: porsche 911, land rover defender 90, bmw e30 m3. You're only charged for the ones we actually find — a miss costs nothing. ## `includeCompsSummary` (type: `boolean`): Adds one row per search with the median, 25th and 75th percentile, low, high, the last-90-day against the 91-to-180-day median and the trend. Worked out from the sold lots this run read, no extra requests. Billed as its own event. ## `maxLots` (type: `integer`): Newest first (or highest first), 36 per page and one page per second. Up to 2,000. The summary is computed from these lots, so a trend needs a long enough read: about 300 lots for a car with a few sales a week. ## `soldOnly` (type: `boolean`): On: only lots that sold. Off: also lots where bidding stopped below the reserve (result bid-to) and withdrawn lots. Asked of Bring a Trailer itself. The comps summary only ever uses sold lots. ## `yearFrom` (type: `integer`): Earliest model year. Asked of Bring a Trailer itself. ## `yearTo` (type: `integer`): Latest model year. Asked of Bring a Trailer itself. ## `period` (type: `string`): Only auctions that ended within this period. Asked of Bring a Trailer itself. ## `endedAfter` (type: `string`): YYYY-MM-DD. Applied after the fetch, on the end date Bring a Trailer prints, so it can be any date. Combine with Ended within to read less. ## `sortBy` (type: `string`): Recently closed first reads the newest comps. Highest price first reads the top of the market (a cut-off date then cannot end the read early). ## `vehiclesOnly` (type: `boolean`): Bring a Trailer also sells parts, manuals and memorabilia. On: keeps lots whose title carries a model year, which drops them. Turn off to keep every lot. Applied after the fetch. ## `deltaMode` (type: `boolean`): Turns the actor into an alert feed. Each run compares every lot of a search with the lots that search returned before and marks it new or seen. Schedule it daily and combine with 'Only return new alerts' and 'Send alerts to'. ## `deltaName` (type: `string`): Leave empty and one is derived from the sold / year / period settings. Type your own name to keep one memory across changes, or to run several independent watchlists. ## `alertOn` (type: `string`): new-result alerts on every lot not seen before. The price rules alert on a new sold lot at or above, or at or below, the price below. ## `alertPriceUsd` (type: `integer`): Needed for the two price rules: the level in US dollars. ## `skipFirstRun` (type: `boolean`): The first run of a search has nothing to compare with. Turn this on to remember its lots without returning or billing them, so alerts start from the second run. ## `alertOnChangeOnly` (type: `boolean`): With monitoring on, a run returns only the new lots that match your alert rule. Lots seen before write no row and are not billed. ## `notifyUrl` (type: `string`): Optional. After a lot is billed, each new lot that matches your alert rule is posted here as one message with the title, price, end date and a link. Discord or Slack: paste the channel's webhook URL. Telegram: https://api.telegram.org/bot/sendMessage?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`): Up to 100. After this, one 'more alerts' message says the rest are in the run's dataset. 0 sends only that one 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. Keep a lot only if its title contains at least one of these words. Applied after the fetch; not billed for the lots it drops. ## `excludeKeywords` (type: `array`): Optional. Drop any lot whose title contains one of these words. Applied after the fetch. ## `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. ## `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": [ "porsche 911" ], "includeCompsSummary": true, "maxLots": 36, "soldOnly": true, "period": "any", "endedAfter": "", "sortBy": "recent", "vehiclesOnly": true, "deltaMode": false, "deltaName": "", "alertOn": "new-result", "skipFirstRun": false, "alertOnChangeOnly": false, "notifyFormat": "auto", "maxNotificationsPerRun": 20, "testRun": false, "onlyFound": false, "includeKeywords": [], "excludeKeywords": [], "columns": [ "rowType", "search", "title", "year", "make", "model", "result", "currency", "finalPrice", "finalPriceUsd", "highBidUsd", "endDate", "endedAt", "noReserve", "location", "lotUrl", "lotId", "checkedAt", "changeType", "alertMatch", "matchesOnSite", "count", "soldCount", "medianUsd", "p25Usd", "p75Usd", "lowUsd", "highUsd", "last90dCount", "last90dMedianUsd", "prior90dCount", "prior90dMedianUsd", "trendPct", "newestEndDate", "oldestEndDate" ], "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 '' with your token const client = new ApifyClient({ token: '', }); // Prepare Actor input const input = { "searches": [ "porsche 911" ], "includeCompsSummary": true, "includeKeywords": [], "excludeKeywords": [] }; // Run the Actor and wait for it to finish const run = await client.actor("accountable_eel/bring-a-trailer-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 '' with your token. client = ApifyClient("") # Prepare the Actor input run_input = { "searches": ["porsche 911"], "includeCompsSummary": True, "includeKeywords": [], "excludeKeywords": [], } # Run the Actor and wait for it to finish run = client.actor("accountable_eel/bring-a-trailer-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": [ "porsche 911" ], "includeCompsSummary": true, "includeKeywords": [], "excludeKeywords": [] }' | apify call accountable_eel/bring-a-trailer-sold-lookup --silent --output-dataset ``` ## MCP server setup ```json { "mcpServers": { "apify": { "type": "http", "url": "https://mcp.apify.com/?tools=fetch-actor-details,accountable_eel/bring-a-trailer-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 ` 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/LbNj2V22w7JxcmJ9u/builds/sNqiDgUNYhENIPLrs/openapi.json