## Whatnot Seller Inventory Scraper
**๐ฐ $2.20 / 1 000 results** ย ยทย pay only for results ย ยทย no credit card to try
*The devil's in the data โ we go fetch it.* ๐
Track any **Whatnot seller's live shop inventory** โ price, quantity, status, transaction type, sales channels โ or search the PRODUCT listings surface by keyword. Built for scheduled monitoring, not one-off lookups.
***
### ๐ฅ What this scrapes
Give this Actor a list of **Whatnot seller usernames** (or profile URLs) and it returns every active listing in each seller's shop โ the same data Whatnot's own storefront shows, structured for export. It also accepts **search keywords** as a secondary mode, pulling rows off the `PRODUCT` search vertical.
Every row carries: listing id, title, subtitle, description, price (amount + currency), listing status, transaction type (`BUY_IT_NOW` / `AUCTION`), quantity, seller username + star rating, product id, image URLs, and sales-channel ids.
### โจ Features
- **Seller-first design.** The lead use case is tracking a known list of sellers' inventory over time, not blind keyword search โ run it on a schedule and diff the output.
- **Keyword search mode.** Add `searchKeywords` alongside or instead of sellers to pull rows off the `PRODUCT` vertical.
- **Fault-isolated per target.** One bad username or a keyword the API can't answer never sinks the run โ every other seller/keyword in the batch still lands.
- **Pydantic-validated rows.** Every dataset item is schema-checked before it's pushed; malformed API rows are skipped, not shipped.
- **Pay only for results.** No data โ no per-row charge, only the small run warm-up fee.
### ๐ฏ Use cases
- **Resellers tracking competitor shops** โ watch a shortlist of sellers' active listings and prices, scheduled daily or hourly.
- **Drop/restock alerting** โ diff successive runs to catch new listings or price changes the moment they post.
- **Category and keyword research** โ sample what's actively listed for a given search term before sourcing inventory yourself.
- **Marketplace intelligence tools** โ feed Whatnot inventory data into a pricing or demand dashboard alongside other marketplaces.
### โ๏ธ How to use it
1. Add one or more entries to `sellerUsernames` โ a bare username (`city_sole`) or a full profile URL (`https://www.whatnot.com/user/city_sole`) both work.
2. Optionally add `searchKeywords` to also pull PRODUCT search results for those terms.
3. Adjust `maxListingsPerSeller` / `maxListingsPerKeyword` if you want fewer rows than the default cap.
4. Run it. Rows land in the dataset as each target finishes, so you can start reading before the run ends.
### ๐ฅ Input
| Field | Type | Default | Description |
|---|---|---|---|
| `sellerUsernames` | array of strings | `["city_sole", "ayden_snkrs", "bamasoles"]` | Seller usernames or profile URLs. Primary input mode. |
| `searchKeywords` | array of strings | `[]` | Keyword search terms against the PRODUCT vertical. Secondary input mode. |
| `maxListingsPerSeller` | integer | `100` | Cap on listings fetched per seller (max 1050). |
| `maxListingsPerKeyword` | integer | `100` | Cap on listings fetched per keyword (max 1050). |
| `proxyConfiguration` | object | BUYPROXIES94952, US | Apify Proxy โ pinned to a US datacenter exit; not user-overridable. |
```json
{
"sellerUsernames": ["city_sole", "ayden_snkrs"],
"searchKeywords": ["jordan 1"],
"maxListingsPerSeller": 100,
"maxListingsPerKeyword": 100
}
```
### ๐ค Output
One row per listing, unified across both input modes:
```json
{
"source": "seller",
"source_value": "city_sole",
"listing_id": "TGlzdGluZ05vZGU6MjI4ODY1NjY4OA==",
"title": "Custom Designed Trainer Deposit",
"subtitle": "New",
"price_amount": 9000,
"price_currency": "GBP",
"listing_status": "ACTIVE",
"transaction_type": "BUY_IT_NOW",
"quantity": 99,
"current_bid_amount": null,
"current_bid_currency": null,
"current_bid_count": null,
"seller": { "username": "city_sole", "rating_overall": 5.0, "rating_num_reviews": 107 },
"product_id": "UHJvZHVjdE5vZGU6NjAzNzQwMTU4",
"image_urls": ["https://images.whatnot.com/..."],
"sales_channel_ids": ["city_sole"],
"listing_url": "https://www.whatnot.com/user/city_sole",
"scraped_at": "2026-09-16T12:00:00+00:00"
}
```
### ๐ฐ Pricing
Pay-Per-Event, no subscription:
| Event | Price |
|---|---|
| Actor start | $0.20 flat, per run |
| Listing scraped | $0.002 per row pushed |
That's **$2.20 per 1,000 results** all-in (run fee + 1,000 rows). A 3-seller monitoring run pulling ~150 listings costs about $0.50.
### ๐ง Limitations
- **`currentBid` is always null.** Live auction bid state isn't exposed on the search/shop surface โ only static listing data.
- **One query tops out around 1,050 rows**, regardless of how many total results the API reports. Breadth comes from adding more sellers or keywords, not raising the per-target cap.
- **No livestream or auction-in-progress data** โ this Actor covers static shop/search listings, not live-show state.
### โ FAQ
**Does this need a Whatnot login or cookies?**
No. The GraphQL endpoint this Actor calls answers unauthenticated requests.
**Can I track the same sellers on a schedule?**
Yes โ that's the primary use case. Schedule the Actor and diff successive dataset exports for new/changed listings.
**Why is `current_bid_amount` always null?**
Whatnot doesn't expose live bid state on this data surface. Live auction pricing needs the livestream itself, which is out of scope here.
**What happens if a username doesn't exist?**
That target reports zero rows and the run still succeeds โ it does not fail the whole batch.
### Your feedback
Found a field that changed shape, or a seller Whatnot renamed? Message us through the Apify Console โ we watch every DevilScrapes Actor's issues and ship fixes fast.
# Changelog
This Actor's version history is a separate document: https://apify.com/devilscrapes/whatnot-seller-inventory-scraper/changelog.md
# Actor input Schema
## `sellerUsernames` (type: `array`):
Whatnot seller usernames or profile URLs (e.g. "city\_sole" or "https://www.whatnot.com/user/city\_sole"). Primary input mode โ each seller's full active shop inventory is fetched.
## `searchKeywords` (type: `array`):
Optional keyword search terms against the PRODUCT listings vertical (secondary input mode). Each keyword returns up to ~1,050 rows before the API's own cursor cap.
## `maxListingsPerSeller` (type: `integer`):
Cap on listings fetched per seller. The shop feed paginates in pages of up to 50 (page sizes above 50 return 200 OK with zero rows โ a documented API trap), so this is rounded up to the nearest multiple of 50 internally.
## `maxListingsPerKeyword` (type: `integer`):
Cap on listings fetched per search keyword. The API tops out at ~1,050 rows per query regardless of totalCount โ breadth comes from adding more keywords/sellers, not raising this value.
## `proxyConfiguration` (type: `object`):
Apify Proxy configuration. Pinned to the BUYPROXIES94952 datacenter group with a US exit โ recon (2026-09-15) measured a non-US exit re-ranking search results toward non-USD currencies and mixing in wrong-region inventory. Not user-overridable on the group/country; client.py hardcodes both regardless of what's set here.
## Actor input object example
```json
{
"sellerUsernames": [
"city_sole",
"ayden_snkrs",
"bamasoles"
],
"searchKeywords": [
"jordan 1"
],
"maxListingsPerSeller": 100,
"maxListingsPerKeyword": 100,
"proxyConfiguration": {
"useApifyProxy": true,
"apifyProxyGroups": [
"BUYPROXIES94952"
],
"apifyProxyCountry": "US"
}
}
```
# Actor output Schema
## `datasetItems` (type: `string`):
All dataset items as JSON.
## `datasetItemsCsv` (type: `string`):
Same data exported to CSV.
## `datasetView` (type: `string`):
Open the run dataset in the Console.
# 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 '