# Bring a Trailer Scraper: Completed Car Auction Results (`scrapingmonkey/bring-a-trailer-scraper`) Actor

Export Bring a Trailer completed auction results with lot titles, result text, auction outcomes, end dates, images and published result amounts. Compare collector-car outcomes while keeping sold prices distinct from unsold bids.

- **URL**: https://apify.com/scrapingmonkey/bring-a-trailer-scraper.md
- **Developed by:** [ScrapingMonkey](https://apify.com/scrapingmonkey) (community)
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.00 / 1,000 results

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

Extract completed Bring a Trailer auctions with result text, published bids, sold prices, end dates and original listing links. **Bring a Trailer Scraper** builds source-linked auction records for comparable-sales research while keeping an unsold bid separate from a confirmed sale.

Build a comparable-sales reference from completed enthusiast-car auctions, keeping published outcomes separate from bids on unsold cars. Keep comparable records in a spreadsheet, purchasing shortlist or recurring market report, with a link back to each source listing.

| At a glance | Details |
|---|---|
| 📥 Input | Search fields or links to the selected items; see the examples below |
| 📤 Output | One row per auction result |
| 📄 Pagination | Automatic up to `maxResults` for each input, when more results are available |
| 🔐 Login required | No |
| ⚡ Processing | Multiple inputs per run with automatic retries for temporary errors |
| 💾 Delivery | One complete Apify dataset table; CSV, JSON and Excel export |

### What the Bring a Trailer scraper collects 🚗

Collect Bring a Trailer auction results with lot titles, published outcomes, bids, dates and original listing links when available.

| Collection | What you receive |
|---|---|
| Bring a Trailer auction results scraper | Auction records with source links, titles and the published result or listing information. |

Data can include:

- Auction identity: Listing ID, auction title and original auction URL
- Vehicle context: Published model year, listing excerpt and country
- Auction outcome: Published result text and sold or unsold outcome
- Price and currency: Published bid and currency; sold price when the result identifies a sale
- Dates and images: Auction end date and listing thumbnail URL
- Sale attributes: Published no-reserve flag and result text

### How to scrape Bring a Trailer 🚀

1. Open the Actor input form.
2. Fill in the search fields, or paste links to the items you want to collect.
3. Set the maximum results and any optional filters.
4. Start the Actor and review the collected rows.
5. Export the dataset or connect it to your application.

#### Bring a Trailer auction results scraper — input example

```json
{
  "mode": "bat_search",
  "keywords": "Ford",
  "maxResults": 10
}
```

`maxResults: 10` means up to 10 results for **each input**. It does not guarantee that the website has that many matches. You can set the limit as low as 1.

### Bring a Trailer data fields and complete output 📦

| Field group | Included data |
|---|---|
| Auction identity | Listing ID, auction title and original auction URL |
| Vehicle context | Published model year, listing excerpt and country |
| Auction outcome | Published result text and sold or unsold outcome |
| Price and currency | Published bid and currency; sold price when the result identifies a sale |
| Dates and images | Auction end date and listing thumbnail URL |
| Sale attributes | Published no-reserve flag and result text |

Each collected item is a separate row. `input` identifies the submitted value and `result_type` identifies the selected mode. All returned fields appear in one table; columns that do not apply to a mode can be empty.

A complete JSON result is shown for every collection mode below, in the same order as the input examples. Each example includes every field for its mode; text and lists are not shortened. Values are representative and can change.

#### Bring a Trailer auction results scraper — complete JSON result

```json
{
  "result_type": "bat_search",
  "input": "https://bringatrailer.com/auctions/results/",
  "status": "success",
  "id": "122213332",
  "url": "https://bringatrailer.com/listing/herb-adams-vse-cobra-replica-2/",
  "title": "428-Powered Herb Adams VSE Cobra 427 Replica 4-Speed",
  "make": null,
  "model": null,
  "variant": null,
  "year": null,
  "price": null,
  "currency": "USD",
  "price_text": null,
  "mileage": null,
  "mileage_unit": null,
  "mileage_text": null,
  "vin": null,
  "body_type": null,
  "fuel_type": null,
  "transmission": null,
  "drive_type": null,
  "engine": null,
  "colour": null,
  "condition": null,
  "description": "This Cobra 427 replica was acquired as a kit by the seller's grandfather in 1995 from Herb Adams VSE of Carmel, California, and completed in 2012. Power comes from a 428ci V8 linked with a Toploader four-speed manual transmission and a 9\" rear end, and the car rides on multi-piece 17\" Compomotive alloy wheels as well as adjustable coilover...",
  "description_html": null,
  "location": null,
  "country": "US",
  "seller.id": null,
  "seller.name": null,
  "seller.type": null,
  "seller.url": null,
  "images": [
    "https://bringatrailer.com/wp-content/uploads/2026/09/1965_shelby_cobra-replica_1965_shelby_cobra-replica_08e1083a-87ae-4392-b938-45b3272c0999-EH0eXD-41447-41448-scaled-lGPtUx.jpg?w=470&h=318&crop=1"
  ],
  "features": null,
  "attributes.name": [
    "no_reserve",
    "result_text"
  ],
  "attributes.value": [
    "False",
    "Sold for USD $42,751 on 9/19/2026"
  ],
  "auction_status": "Sold for USD $42,751 on 9/19/2026",
  "current_bid": 42751.0,
  "sale_price": 42751.0,
  "bid_count": null,
  "auction_end": "2026-09-19T19:31:54+00:00",
  "published_at": null,
  "updated_at": null,
  "inspection_url": null
}
```

Images, tags and other lists stay with their parent result instead of creating extra rows. Invalid or unavailable inputs, inputs with no results, and requests that fail after all retries produce a row with `status: failed`. At most one failed row is saved per input; it includes `error_code` and `error_message` explaining the outcome. A normal end of pagination after collected results does not add a failed row.

### Input requirements and collection settings ⚙️

| Setting | What to enter |
|---|---|
| **Maximum results per search or link** (`maxResults`) | Collect up to this many results for each search or link. Minimum: 1. |
| **Keywords** (`keywords`) | Words to look for, for example Ford Focus. |
| **Year from** (`yearFrom`) | Earliest year of manufacture. |
| **Year to** (`yearTo`) | Latest year of manufacture. |

| Collection mode | Fields to use |
|---|---|
| Auction Results | **Keywords**, **Year from**, **Year to** |

The result limit applies separately to each search or supplied link. Collection ends earlier when no more matching results are available.

### Bring a Trailer scraping use cases 🎯

#### Build auction comparables

Compare the published auction figures for similar vehicles on Bring a Trailer, retaining each lot link for a closer review.

#### Study completed auction results

Separate sold results from other published outcomes before building an enthusiast-car comparable-sales dataset.

#### Compare sold and unsold outcomes

Use the published result text to distinguish confirmed sales from bids on vehicles that did not sell.

#### Review no-reserve results

Use the published no-reserve attribute and result text to compare outcomes across the collected auctions.

#### Prepare valuation reports

Add source-linked Bring a Trailer auction records to vehicle valuation reports alongside other comparable vehicles.

### Pricing and saved-result behavior 💰

See the Actor's **Pricing** tab for the active pricing model and current rate. Store settings may change, so this README does not claim a fixed cost.

Under dataset-item pricing:

- Each collected item saved in the dataset is one result.
- Images, tags and other values attached to that item do not create additional rows.
- Automatic retry attempts do not create extra dataset rows.
- A saved `failed` row is also one billable dataset item, including invalid inputs, unavailable items, no results, or exhausted retries. At most one failed row is saved per input, including when some results were already collected.
- `maxResults` caps all saved rows for each input, including its failed row. Repeated copies of the same input are processed once. More inputs or a higher limit can produce more saved results.

### Bring a Trailer scraper API and integrations 🔌

Replace `$ACTOR_ID` with the ID shown in the Actor API tab and `$APIFY_TOKEN` with your token.

```bash
curl -X POST "https://api.apify.com/v2/acts/$ACTOR_ID/runs?token=$APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"mode":"bat_search","keywords":"Ford","maxResults":10}'
```

Use schedules for recurring collection, webhooks for completion notifications, and Apify integrations for Google Sheets, Make, Zapier, cloud storage, a CRM or your own application.

### Reliability, retries, and public-data limits ⚠️

Temporary connection errors, timeouts and access restrictions are retried automatically, up to five attempts. Invalid inputs save a failed row without an HTTP request; confirmed unavailable items save a failed row without unnecessary retries. Exhausted retries also save a failed row. Results already collected remain available if a later request fails, and normal pagination completion adds no error row. Collection also stops after two consecutive fully processed pages add no new results, even if the website provides another cursor. Required detail lookups are completed before checking a page; new results reset the counter, and independent reply branches are checked separately. Failures while initializing the Actor, saving data or scheduling requests stop the run instead of being reported as a failed website result.

Coverage is the auction-results catalogue; a published bid is not treated as a sale price unless the result states that the car sold.

Optional fields are available only when the website publishes them.

Bring a Trailer controls which information is publicly available. Removed, private or restricted items may be unavailable, and optional values can be null or empty. A run can still fail if the results cannot be saved.

### Frequently asked questions ❓

#### Does it require an account on Bring a Trailer?

No. You do not need to provide an account, password or login cookies. Only publicly available information is collected.

#### How does maxResults work?

It limits the number of saved results separately for every input. The minimum is 1. With maxResults set to 10, each input returns at most 10 available results.

#### What can I use to search Bring a Trailer?

Choose keywords, year from, year to in the input form.

#### Are bids and sold prices treated as the same value?

No. A sold price is recorded when the published result says the car sold. Other visible bids remain separate from confirmed sale results.

#### Why are some fields empty?

The website may not publish that value, or the field may belong to a different collection mode. Missing values remain null or empty instead of being guessed.

#### Can I export the results to a spreadsheet?

Yes. Download CSV, Excel or JSON from the Apify dataset. All returned fields are included in the same results table.

### Support and responsible use 🛟

For a reproducible issue, share the run ID, selected mode, result limit and a safe public example through the support channel. Never disclose access tokens, passwords or proxy credentials.

Use public Bring a Trailer information lawfully and responsibly. Follow applicable privacy, copyright, data-protection, contractual and platform requirements when storing, analyzing or redistributing results.

# Actor input Schema

## `mode` (type: `string`):

Choose the information to collect.

## `maxResults` (type: `integer`):

Collect up to this many results for each search or link. Minimum: 1.

## `keywords` (type: `string`):

Words to look for, for example Ford Focus.

## `yearFrom` (type: `integer`):

Earliest year of manufacture.

## `yearTo` (type: `integer`):

Latest year of manufacture.

## Actor input object example

```json
{
  "mode": "bat_search",
  "maxResults": 10,
  "keywords": "Ford"
}
```

# Actor output Schema

## `results` (type: `string`):

Collected entities and failed input outcomes, with all available fields and error explanations in one dataset.

# 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 = {
    "mode": "bat_search",
    "maxResults": 10,
    "keywords": "Ford"
};

// Run the Actor and wait for it to finish
const run = await client.actor("scrapingmonkey/bring-a-trailer-scraper").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 = {
    "mode": "bat_search",
    "maxResults": 10,
    "keywords": "Ford",
}

# Run the Actor and wait for it to finish
run = client.actor("scrapingmonkey/bring-a-trailer-scraper").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 '{
  "mode": "bat_search",
  "maxResults": 10,
  "keywords": "Ford"
}' |
apify call scrapingmonkey/bring-a-trailer-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,scrapingmonkey/bring-a-trailer-scraper"
        }
    }
}
```

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/PHHXxFUWOQmzWNexJ/builds/do2ydlW9wUccic4TT/openapi.json