# eBay Sold Comps Scraper — Real Sold Prices, Median & Range (`stripy_nonchalance/grail-ebay-sold-listings`) Actor

One keyword in, up to 240 completed eBay sales out. Every row carries the final price, sale date, condition, seller, shipping and a link; every run adds a median, min and max. Completed sales only — no asking prices.

- **URL**: https://apify.com/stripy_nonchalance/grail-ebay-sold-listings.md
- **Developed by:** [Hudson Bales](https://apify.com/stripy_nonchalance) (community)
- **Categories:** E-commerce, Automation, Developer tools
- **Stats:** 1 total users, 0 monthly users, 0.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$2.50 / 1,000 sold listings

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

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

## eBay Sold Comps — one keyword in, a usable price out

Feed it a keyword, get **real eBay sold comps** back: up to **240** completed sales, each
carrying the final price, sale date, condition, seller, shipping and a link to the item —
**plus a median, min and max** for the whole run. The number you were after, not just a
heap of rows.

Completed sales only. Active listings and unsold items are filtered out, so asking prices
never enter the sample.

### Why this one

- **Insight, not just rows.** Every run returns a summary — count, median sold price, min, max. No client-side math needed for a sanity check.
- **Depth.** Up to **240** rows in a single run, not one page.
- **36 structured fields per listing** (table below). A plain sold-listings grab gives you a handful.
- **8 eBay marketplaces** from one input.
- **Cache-first** — repeat keywords come back fast.
- **Same data as our API.** This actor is a thin client over Grail's own sold-comps engine, so what you see here is exactly what our paid API serves.

### Output

One dataset row per sold listing. Key fields:

| field | type | notes |
|---|---|---|
| `itemId` | string | eBay item id |
| `url` | string | canonical item URL |
| `title` | string | listing title |
| `soldPrice` | string | final sold price (decimal string) |
| `soldCurrency` | string | ISO currency, e.g. `USD` |
| `totalPrice` | string | item + shipping, when both known |
| `endedAt` | string | sale / end date |
| `condition` | string | condition label |
| `buyingFormat` | string | `auction` | `best offer` | `fixed price` |
| `bestOfferAccepted` | boolean | Best Offer accepted? |
| `bidCount` | integer | bids, for auctions |
| `sellerUsername` | string | seller handle |
| `sellerFeedbackScore` | integer | seller feedback count |
| `sellerPositivePercent` | number | seller positive % |
| `shippingPrice` | string | shipping cost, when shown |
| `shippingType` | string | `free` | `paid` |
| `itemLocation` | string | item location |
| `thumbnailUrl` | string | listing image |
| `scrapedAt` | string | fetch timestamp |
| …plus | | `epid`, `categoryId`, `conditionId`, `listingType`, `sellerType`, `fullResThumbnailUrl`, `unitsSold`, `watcherCount`, `boa*` |

The **36-field item contract** matches Grail's sold-comps API exactly.

#### Run summary

Alongside the rows, the run writes a `SUMMARY` record to the key-value store:

```json
{
  "count": 120,
  "pricedCount": 118,
  "currency": "USD",
  "medianSoldPrice": "48.50",
  "minSoldPrice": "9.99",
  "maxSoldPrice": "410.00"
}
```

### Input

| field | type | default | notes |
|---|---|---|---|
| `keyword` | string | — | product / model / MPN (required) |
| `count` | integer | 60 | 1–240 |
| `country` | enum | `com` | eBay domain: `com` (US), `co.uk`, `de`, `fr`, `it`, `es`, `ca`, `com.au` |

#### Example input

```json
{ "keyword": "charizard base set holo", "count": 120, "country": "com" }
```

#### Example row

```json
{
  "itemId": "366693551593",
  "title": "Charizard 004/102 Base Set Holo Rare 1999 Pokemon TCG",
  "soldPrice": "128.50",
  "soldCurrency": "USD",
  "endedAt": "2026-10-08",
  "condition": "Pre-Owned",
  "sellerUsername": "poke_shop"
}
```

### Pricing

**$2.50 per 1,000 sold listings** — charged per result, by Apify. No subscription.

### Also available as an API

Prefer your own key and quota, the async job queue for deep pagination, and no
marketplace markup? The same data is served directly at **https://grail.solutions**
(free key: 100 requests/month).

### Configuration (actor secret)

Set the actor's `GRAIL_API_KEY` secret env var (Apify Console → Actor → Settings →
Environment variables) to a Grail API key. Optional `GRAIL_API_BASE` overrides the API
host (default `https://grail.solutions`). Without a key the actor falls back to scraping
eBay directly.

### Limits

- 1–240 results per run.
- Questions or a field you need? Open an issue on the actor's Apify page.

# Actor input Schema

## `keyword` (type: `string`):

Product name, model, or MPN to search eBay sold listings for.

## `count` (type: `integer`):

Maximum number of sold listings to return.

## `country` (type: `string`):

eBay domain to search (com = US, co.uk = UK, com.au = Australia, …).

## Actor input object example

```json
{
  "count": 60,
  "country": "com"
}
```

# Actor output Schema

## `soldListings` (type: `string`):

One row per sold eBay listing (price, date, condition, seller, shipping, URL).

## `summary` (type: `string`):

Count, median, min and max sold price for the run.

# 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 = {};

// Run the Actor and wait for it to finish
const run = await client.actor("stripy_nonchalance/grail-ebay-sold-listings").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 = {}

# Run the Actor and wait for it to finish
run = client.actor("stripy_nonchalance/grail-ebay-sold-listings").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 '{}' |
apify call stripy_nonchalance/grail-ebay-sold-listings --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,stripy_nonchalance/grail-ebay-sold-listings"
        }
    }
}
```

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/1J1bJDm3FxOuK1BUw/builds/Hy7onnAfVEr941ZhQ/openapi.json