# eBay Listing Details Scraper - Item Data, Specifics & Seller (`scrapeworks/ebay-listing-details`) Actor

Get full eBay listing details in bulk from item IDs or URLs: title, price, condition, item specifics, seller feedback, shipping, returns, sold count and all image URLs as clean JSON. No eBay API key or login needed.

- **URL**: https://apify.com/scrapeworks/ebay-listing-details.md
- **Developed by:** [Nicolas van Arkens](https://apify.com/scrapeworks) (community)
- **Categories:** E-commerce, Lead generation
- **Features:** Limited permissions
- **Stats:** 14 total users, 6 monthly users, 96.3% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.50 / 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.

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 Listing Details Scraper — Item Data, Specifics, Seller & Photos

**Turn a list of eBay item IDs or URLs into clean, structured listing data.** Paste the
links (or IDs) of the eBay listings you care about and get back the full details of each
one as JSON: title, price and currency, condition, **every item specific** (Brand, Model,
Type, MPN …), the **seller and their feedback**, shipping, returns, item location, sold
count, the category breadcrumb and **all high-resolution photo URLs**.

No eBay API key, no developer account, no login. This is the zero-setup equivalent of the
eBay Browse API's *getItem* endpoint — you bring item IDs/URLs, it returns the listing data.

> 🔎 Need to **find** the listings first? Use the **eBay Search Scraper** to turn keywords
> into a list of item IDs, then feed those IDs into this actor to enrich each one with the
> data only the item page carries (item specifics, full condition text, seller feedback,
> every photo).

### What you get (one row per listing)

| Field | Description |
|---|---|
| `itemId` | eBay item ID |
| `url` | Canonical listing URL |
| `title` | Full listing title |
| `price` / `priceValue` / `priceMax` / `currency` | Raw price text, numeric value(s) and currency. Ranges and "or Best Offer" are handled |
| `priceConverted` | eBay's approximate price in your local currency, when shown |
| `condition` / `conditionDescription` | Short condition (e.g. "Open box") + eBay's full condition note |
| `itemSpecifics` | Object of every item-specific the seller filled in (Brand, Model, Type, Size, Color …) |
| `seller` | `{ username, url, feedbackScore, positivePercent }` |
| `shipping` | Shipping/postage text |
| `returns` | Returns policy text |
| `itemLocation` | Where the item ships from |
| `quantitySold` / `quantityAvailable` | Sold count / quantity available, when displayed |
| `breadcrumbs` | Category path, e.g. `["eBay","Jewelry & Watches","Watches",…]` |
| `images` / `mainImage` | De-duplicated high-resolution (`s-l1600`) photo URLs for this listing's gallery |
| `domain` / `scrapedAt` | Marketplace + ISO timestamp |

### Input

Provide listings any way you like — bulk is the point:

- **`itemUrls`** — a list of full eBay listing URLs (any marketplace: .com, .co.uk, .de …).
- **`itemIds`** — a list of bare numeric item IDs, looked up on the **`domain`** you choose.
- **`maxItems`** — safety cap on how many to fetch in one run.
- **`proxyConfiguration`** — eBay blocks datacenter traffic, so **Residential** Apify Proxy
  is strongly recommended.

```json
{
  "itemUrls": [
    "https://www.ebay.com/itm/306919649765",
    "https://www.ebay.co.uk/itm/168393471627"
  ],
  "itemIds": ["287371338722"],
  "domain": "ebay.com",
  "maxItems": 1000,
  "proxyConfiguration": { "useApifyProxy": true, "apifyProxyGroups": ["RESIDENTIAL"] }
}
```

### Output sample

```json
{
  "itemId": "306919649765",
  "url": "https://www.ebay.com/itm/306919649765",
  "title": "Antique WWII Era Military Officer's Omega GMT Wristwatch -c.1940 - 48mm- Working",
  "price": "US $2,764.80 or Best Offer",
  "priceValue": 2764.8,
  "currency": "US $",
  "priceConverted": "Approximately DKK 17,862.27",
  "condition": "Pre-owned - Good",
  "seller": {
    "username": "Riaerica Antiques and Collectables",
    "url": "https://www.ebay.com/str/riaericaantiquesandcollectables",
    "feedbackScore": 4777,
    "positivePercent": 99.5
  },
  "itemSpecifics": {
    "Brand": "OMEGA",
    "Department": "Men",
    "Type": "Wristwatch",
    "Country of Origin": "Switzerland"
  },
  "shipping": "Free Standard International Shipping",
  "returns": "Seller does not accept returns. See details for returns",
  "itemLocation": "Sofia, Bulgaria",
  "breadcrumbs": ["eBay", "Jewelry & Watches", "Watches, Parts & Accessories", "Watches", "Wristwatches"],
  "images": ["https://i.ebayimg.com/images/g/-q0AAOSw6nFoLwai/s-l1600.jpg"],
  "mainImage": "https://i.ebayimg.com/images/g/-q0AAOSw6nFoLwai/s-l1600.jpg",
  "domain": "ebay.com",
  "scrapedAt": "2026-06-14T20:01:19Z"
}
```

### Use cases

- **Repricing & competitor monitoring** — track the exact price, condition and seller of a
  watch-list of listings over time.
- **Catalog / product enrichment** — pull item specifics and photos to build or fill out a
  product database from eBay listings.
- **Reseller & sourcing research** — capture seller feedback, item location and the full
  spec sheet for listings you're evaluating.
- **Lead lists** — extract the seller (and their store URL) behind a set of listings.

### FAQ

**Do I need an eBay API key or developer account?** No. This reads eBay's public listing
pages, so there is nothing to register and no OAuth to manage.

**Where do I get item IDs?** They're the 12–13 digit number in any eBay listing URL
(`ebay.com/itm/`**`306919649765`**). The companion **eBay Search Scraper** produces them in
bulk from keywords.

**Which eBay sites are supported?** ebay.com, .co.uk, .de, .com.au, .ca, .fr, .it, .es,
.nl, .ie and .in. Item URLs keep their own marketplace; bare IDs use the `domain` you pick.

**Why is residential proxy recommended?** eBay blocks datacenter IP addresses. Residential
Apify Proxy makes the requests look like a normal browser, which is what reliable results
need.

**What happens to ended or removed listings?** They're detected (404/410), skipped, and
**never charged** — you only pay for listings that return real data.

### Pricing

Pay-per-result: you're charged a small fixed fee for **each listing successfully returned**.
Blocked, missing or empty pages are never charged.

# Actor input Schema

## `itemUrls` (type: `array`):

One or more full eBay listing URLs to fetch details for, e.g. 'https://www.ebay.com/itm/168393471627'. Paste as many as you like in a single run - each is fetched and returned as one row. Works with any eBay marketplace URL (.com, .co.uk, .de, ...). You can provide item URLs here, numeric item IDs in 'Item IDs', or both.

## `itemIds` (type: `array`):

One or more bare numeric eBay item IDs (the 12-digit number from an eBay listing URL, e.g. '168393471627'). Each is looked up on the marketplace chosen below. Use this when you already have a list of IDs (for example from the eBay Search Scraper) and don't want to build full URLs.

## `domain` (type: `string`):

Which eBay site to look up bare item IDs on. Prices are returned in that site's local currency. Item URLs already include their own marketplace, so this only affects IDs entered in 'Item IDs'. Most-used is ebay.com (US).

## `maxItems` (type: `integer`):

Safety cap on the total number of listings fetched in one run (across both URLs and IDs). Extra inputs beyond this number are ignored.

## `proxyConfiguration` (type: `object`):

Proxy used to reach eBay. eBay blocks datacenter traffic, so RESIDENTIAL Apify Proxy is strongly recommended for reliable results. Defaults to Apify Proxy.

## Actor input object example

```json
{
  "itemUrls": [
    "https://www.ebay.com/itm/168393471627",
    "https://www.ebay.com/itm/306919649765"
  ],
  "domain": "ebay.com",
  "maxItems": 1000,
  "proxyConfiguration": {
    "useApifyProxy": true
  }
}
```

# 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 = {
    "itemUrls": [
        "https://www.ebay.com/itm/168393471627",
        "https://www.ebay.com/itm/306919649765"
    ],
    "proxyConfiguration": {
        "useApifyProxy": true
    }
};

// Run the Actor and wait for it to finish
const run = await client.actor("scrapeworks/ebay-listing-details").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 = {
    "itemUrls": [
        "https://www.ebay.com/itm/168393471627",
        "https://www.ebay.com/itm/306919649765",
    ],
    "proxyConfiguration": { "useApifyProxy": True },
}

# Run the Actor and wait for it to finish
run = client.actor("scrapeworks/ebay-listing-details").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 '{
  "itemUrls": [
    "https://www.ebay.com/itm/168393471627",
    "https://www.ebay.com/itm/306919649765"
  ],
  "proxyConfiguration": {
    "useApifyProxy": true
  }
}' |
apify call scrapeworks/ebay-listing-details --silent --output-dataset

```

## MCP server setup

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

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/GDQKZNUpXQ4VZzAGt/builds/BIHPxgg3yTf8Qh0Mh/openapi.json