Poshmark Sold Listings Scraper (US) avatar

Poshmark Sold Listings Scraper (US)

Pricing

from $0.50 / 1,000 listing observations

Go to Apify Store
Poshmark Sold Listings Scraper (US)

Poshmark Sold Listings Scraper (US)

Collect Poshmark US sold-status observations with displayed prices for resale research: sold/active/out-of-stock label, price and raw text, size, listing URL and observation time from one search page or your own listing links. Displayed prices are not verified sale prices.

Pricing

from $0.50 / 1,000 listing observations

Rating

0.0

(0)

Developer

Philip Kirkbride

Philip Kirkbride

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

15 hours ago

Last modified

Categories

Features

Limited permissions

Share

Poshmark US Sold-Status Observations

Collect public Poshmark listing status and displayed prices for US only from https://poshmark.com, in USD. Search for a product or check specific listing links to build a dated set of resale-market observations.

These are listing observations, not verified transaction records. A sold label does not reveal the final sale price or sale date.

What you get

One row per observed listing: the listing id, url and title, the fixed market, locale and currency, the observed sold_status (sold, active or out_of_stock) with the label text that proves it, the displayed price and any secondary price with their raw text, size_raw when shown, how the row was read (source_kind), and a UTC observed_at timestamp.

Typical uses

  • Resale price research: collect displayed prices for a brand, model or keyword and compare them with what similar items ask today.
  • Sold-status tracking: check a set of listing links on a schedule and see which items are still active, sold out or sold.
  • Inventory and sourcing: build a dated observation set for a category and revisit it to see how listings turn over.
  • Comps evidence: keep a reproducible snapshot of the exact labels and prices behind a resale estimate, with the observation time attached.

How it works

  1. Either search one sold-search page with a keyword, or pass 1-48 explicit listing links from https://poshmark.com.
  2. Each row records what the page displays: the status label, the displayed price (and a secondary price when shown) and the size, with the raw text kept beside the parsed value.
  3. Rows go to the dataset for JSON, CSV or Excel export; the run summary states how many observations were saved.

Input

{"query":"rolex book","maxItems":5}
FieldMeaning
queryKeyword search of one sold-search page in this market.
listingUrlsAlternatively, 1-48 public listing URLs from https://poshmark.com.
maxItemsMaximum observations, from 1 to 48; default 5.

Use query or listingUrls, not both. Clear the prefilled query in the input form before entering listing URLs. Empty input searches for rolex book with a maximum of 5 observations. Search covers one page; additional result pages are not supported. Links from another market are not supported.

Output

One row per observed listing, with:

  • id, url and title to identify the listing.
  • Fixed market, locale (en-US) and currency.
  • sold_status: sold, active or out_of_stock, plus the published labels in sold_label_raw and status_evidence.
  • displayed_price and displayed_price_raw, plus any secondary_price and secondary_price_raw. A secondary price does not establish a discount or a previous transaction price. Missing displayed prices remain null.
  • size_raw when available, source_kind, source_url, final_url and UTC observed_at.

actual_sold_price and sold_at are always null. Observation time is not sale time. A Sold Out label does not imply a completed transaction, settlement, offer or bundle total, or cancellation status.

Selected fields from a historical observation; other fields are omitted:

{
"id": "635fe4584bf9ff78ed83345e",
"market": "US",
"locale": "en-US",
"sold_status": "sold",
"displayed_price": 6,
"currency": "USD",
"actual_sold_price": null,
"sold_at": null
}

Pricing

Each run has a small start charge plus a charge for every observation saved to its dataset. A default 5-observation run therefore costs a few cents, and a failed read that saves nothing is not charged per row. See the Actor's Pricing tab for the current amounts.

Limits

  • This Actor is fixed to US; market, currency and locale cannot be changed through input.
  • Complete market coverage and reliable access at scale have not been established.
  • Unavailable pages and uncertain observations produce a clear run error. Searches with no listings currently produce an error rather than an empty result.
  • A run that fails after saving observations may leave partial output. Check the run status before treating a dataset as complete.
  • Final sale prices, sale dates and French-Canada coverage are unavailable.

FAQ

Is a sold listing a completed sale? No. The Actor records the status and price the page displays. Settlement amount, date and payment are never inferred.

Why are actual_sold_price and sold_at always null? Poshmark does not publish them on these pages, so they stay null instead of being guessed.

Why did a search fail with no rows? A page with no listing cards, an unavailable page or an ambiguous status label fails with a message naming the cause. Broaden the keyword or check the links and retry.

How many observations can one run return? Up to 48, from one search page or your selected links; maxItems also caps the saved rows.

Can I collect several search pages? Not in one run: one search page per run. Use a different keyword or exact listing links for more coverage.

Can I run it on a schedule? Yes; each run is a dated observation set, so compare observed_at and sold_status between runs.

Does it collect seller contact details? No. Rows carry listing-level data only, no seller contact information.

Support

Check the Actor's Pricing tab for current rates. For help, contact support from the Actor page and include the run URL.