Poshmark Sold Listings Scraper
Pricing
from $0.30 / 1,000 sold listing saveds
Poshmark Sold Listings Scraper
Export public Poshmark sold-listing prices, brands, sizes, sellers, images and listing URLs for resale comps and pricing research.
Pricing
from $0.30 / 1,000 sold listing saveds
Rating
0.0
(0)
Developer
Fetch Cat
Maintained by CommunityActor stats
0
Bookmarked
7
Total users
2
Monthly active users
5 days ago
Last modified
Categories
Security
Limited permissionsShare
Export public Poshmark sold listings into a dataset for resale comps and pricing research. Search by keyword or supply public search URLs to collect listing prices, brands, sizes, sellers, images and listing links without logging in.
soldPrice is the price present in a sold listing's public search data, not proof of the final negotiated payment. Results cover the available search index, not every historical sale.
Quick start
- Open the Actor and enter a specific query, such as
nike shoes. - Start with 25 records and a small page limit.
- Select your connection settings in the input form, then click Start.
- Review the dataset and export CSV, Excel or JSON.
{"query": "nike shoes","maxItems": 25,"maxPages": 2,"proxyConfiguration": { "useApifyProxy": true }}
Prefer a video guide? This short Apify walkthrough shows you how to set up and run an Actor. It uses a different Actor, but the setup steps are the same.
Ready-to-run examples
Choose an existing example with a small, preconfigured search:
- Coach Tabby sold comps — Review sold-listing prices for a specific bag model.
- Lululemon leggings sold listings — Collect apparel comps with brand and size fields.
- Nike shoes sold listings — Compare shoe listings with public listing links.
What you get
- Collect public sold listings by keyword or public search URL.
- Return listing prices, brands, sizes, categories, condition, public seller fields, images and listing URLs when available.
- Include public like, share and comment counts when available.
- Export individual listing rows for your own comparisons.
The Actor returns listing data, not calculated pricing recommendations, sales velocity or a complete demand report. It does not retrieve private buyer data or detail-page enrichment.
Who is it for?
- Resale pricing: Review comparable listings before pricing your inventory. Calculate your own ranges or medians after checking the sample.
- Sourcing research: Compare brands, models and sizes before buying secondhand stock.
- Market analysis: Build a dataset of public listing metadata for a spreadsheet or dashboard.
Input settings
Provide a non-empty query, at least one startUrls entry, or at least one resumeUrls entry. None is globally required because they are alternatives. Combining them adds searches under one shared record limit.
| Setting | JSON key | Meaning |
|---|---|---|
| Search query | query | Keyword or product phrase for sold listings. |
| Poshmark search URLs | startUrls | Public HTTPS Poshmark /search URLs. Supplied filters are retained while requesting sold listings. |
| Maximum sold listings | maxItems | Total saved-row cap, 1–10,000. Default 50, form prefill 20. |
| Sort order | sortBy | Source ordering for the query-generated search only. |
| Maximum search pages | maxPages | Per-search page cap, 1–100. Default 10. |
| Maximum run time | maxRunSeconds | Time budget, 1–270 seconds. Default 270. |
| Resume search URLs | resumeUrls | Continue from unfinished public search URLs, when saved. |
| Proxy configuration | proxyConfiguration | Connection settings. See the field help for form and API behavior. |
sortBy accepts added_desc, price_desc, price_asc and like_count_desc. The form defaults to Recently added. URL inputs keep their own sorting, and combined results are not globally re-sorted. Source ordering does not guarantee newest sale first.
Output data
One dataset row represents one listing ID. Optional values can be null. Timestamps and prices reflect the public search data available at extraction time. The optional condition field preserves Poshmark's condition code. likeCount, shareCount and commentCount are public engagement counts, with null when unavailable.
Illustrative shape only, not a measured sale:
{"title": "Example sold listing","url": "https://poshmark.com/listing/example-LISTING_ID","listingId": "LISTING_ID","soldPrice": 25,"currency": "USD","originalPrice": 50,"brand": null,"condition": null,"likeCount": null,"shareCount": null,"commentCount": null,"size": null,"category": null,"department": null,"sellerUsername": null,"sellerDisplayName": null,"status": null,"inventoryStatus": "sold_out","imageUrl": null,"createdAt": null,"updatedAt": null,"soldAt": null,"sourceQuery": "nike shoes","scrapedAt": "2026-10-25T00:00:00.000Z"}
| Fields | Meaning |
|---|---|
title, url, listingId | Listing title, public link and identifier. |
soldPrice, currency, originalPrice | Public sold-listing price, currency and original price value when supplied. Zero original prices can be source placeholders. |
brand, size, category, department | Available product classifications. |
condition | Poshmark's condition code when supplied. |
likeCount, shareCount, commentCount | Public engagement counts when supplied. |
sellerUsername, sellerDisplayName | Public seller information when included in search results. |
status, inventoryStatus | Source listing and inventory status values. |
imageUrl | Main listing image URL when present. |
createdAt, updatedAt, soldAt | Source creation, update and inventory/status-change timestamps. soldAt is not an independently verified transaction time. |
sourceQuery, scrapedAt | Query from the source URL, if present, and extraction time. |
RUN_SUMMARY contains the saved count, per-search outcome reasons, source errors and pending URLs. Exhausted searches with no sold matches succeed with an empty dataset and the reason no_matching_sold_listings. Recommendations are not sold matches. PENDING_URLS is saved when unfinished URLs exist, when storage is available. Blocking, request failures or unfinished required extraction fail the run while preserving useful rows. A shorter platform/API timeout takes precedence over maxRunSeconds, including startup and a shutdown reserve.
The form and example use managed Apify Proxy, which can incur proxy usage. Explicit direct settings and customer-supplied proxies remain supported without an automatic paid fallback. Poshmark can block direct access. Omitting proxyConfiguration in API input retains the existing managed-proxy behavior.
Download your results
Open your run's dataset, choose Export and select JSON, CSV or Excel. JSON keeps nested fields together. CSV and Excel are useful when you want to review the records in a spreadsheet.
See Apify's download and export guide for the available formats and field options.
Pricing
This Actor uses pay-per-event pricing. The start event is charged once after initial search and limit validation. Each item event is associated with a sold-listing row saved to the dataset. Summaries and source-error records are not listing rows. A run that saves no rows may still incur the start event.
See the live Pricing tab for current rates and discounts.
Tips for best results
- Start with a specific query. Include a brand or model to make your comps easier to review.
- Keep your first search small. Use bounded
maxItemsandmaxPagesbefore collecting a larger sample. - Check the source listings. Treat public listing prices as comparables, not independently verified transaction payments.
- Review incomplete searches. Check the run summary and recorded unfinished URLs when available.
Limits and caveats
- Only public sold-search data is supported. No login, cookies or private account access is needed.
- Results can be fewer than requested because of available matches, page limits, time limits or source access problems.
- Valid searches with no matches can return an empty dataset. Failed pages can leave a partial dataset. If none of the supplied sources can be read, the run fails.
- The search index can change. The Actor cannot guarantee complete sale history, final negotiated prices or a globally sorted combined dataset.
- Resume URLs cover recorded unfinished work, not necessarily every failed page or search stopped at a result/page cap.
Automation and integrations
Save your settings for next time
Once you have an input that works for you, save it as an Apify task. This keeps your settings together so you can use them again without filling in the form from scratch.
Run on a schedule
Need fresh results regularly? You can schedule the Actor or a saved task to run at a time that suits you.
Each scheduled run collects the data again. If you want to compare results or highlight changes, add that step in your own workflow.
Send results to your other tools
Use n8n, Make or Zapier to connect this scraper to the rest of your workflow. For example, you could pass its results to an AI assistant or add records to a spreadsheet. Follow the Apify integration guides for your chosen tool.
For a custom connection, an Apify webhook can notify your app when a run finishes or fails. Your app can then fetch the results or handle the failure.
API usage
Want to collect this data from your own app or automation? The examples below send input to the scraper and show how to collect its results.
The Node.js and Python examples wait for the run to finish before reading its results. The cURL example starts the run and returns its details. Wait for that run to finish, then use its defaultDatasetId to fetch the results.
For setup instructions, see Apify's JavaScript client guide, Python client guide and Actor runs API reference.
cURL
curl -X POST 'https://api.apify.com/v2/acts/fetch_cat~poshmark-sold-listings-scraper/runs' \-H "Authorization: Bearer $APIFY_TOKEN" \-H 'Content-Type: application/json' \-d '{"query":"nike shoes","maxItems":25,"maxPages":2,"proxyConfiguration":{"useApifyProxy":false}}'
Node.js
import { ApifyClient } from 'apify-client';const client = new ApifyClient({ token: process.env.APIFY_TOKEN });const run = await client.actor('fetch_cat/poshmark-sold-listings-scraper').call({query: 'nike shoes', maxItems: 25, maxPages: 2,proxyConfiguration: { useApifyProxy: false },});const { items } = await client.dataset(run.defaultDatasetId).listItems();console.log(items);
Python
import osfrom apify_client import ApifyClientclient = ApifyClient(os.environ['APIFY_TOKEN'])run = client.actor('fetch_cat/poshmark-sold-listings-scraper').call(run_input={'query': 'nike shoes', 'maxItems': 25, 'maxPages': 2,'proxyConfiguration': {'useApifyProxy': False},})items = client.dataset(run['defaultDatasetId']).list_items().itemsprint(items)
MCP and AI agents
You can ask your AI assistant to collect data with Poshmark Sold Listings Scraper and help you work with the results. The scraper returns the data, and your assistant can then summarize it, compare records or prepare notes.
Connect your assistant through the Apify MCP server. MCP gives your assistant a way to find this scraper, run it and read the results. Follow the official setup and sign-in guide for your app.
Easier setup with an Apify plugin
If you use a supported coding assistant, the official Apify plugin can set up the connection for you. It connects your assistant to Apify and includes instructions for common tasks. Follow the guide for your particular app.
Use Apify AI in Console
Prefer to keep everything in Apify? Open Apify AI in Console and ask it to find Fetch Cat's Poshmark Sold Listings Scraper. You can describe the data you want and ask questions about the results.
Apify AI is currently in beta. It asks for confirmation before starting an Actor, and normal run charges apply.
Choose your assistant
- Claude and Claude Code (Anthropic): Apify setup guide.
- ChatGPT and Codex (OpenAI): Apify setup guides.
- Grok Bot (xAI): Apify plugin guide.
- Gemini CLI (Google): MCP server setup guide. Use the server URL below with the HTTP configuration supported by Gemini CLI.
Connect just this scraper
To keep your setup focused on this scraper, add this server configuration to a compatible MCP client:
{"mcpServers": {"apify": {"url": "https://mcp.apify.com?tools=fetch_cat/poshmark-sold-listings-scraper"}}}
Sign in to Apify when your client asks. If your client uses a Bearer token instead, follow its setup guide and keep the token in its secure configuration. Configuration formats vary by app, so use the linked guide if your client needs a different format.
Use Apify's general server
Already connected to the general Apify MCP server at https://mcp.apify.com? You can use it to find this scraper without adding another server. Ask your assistant to use Poshmark Sold Listings Scraper by Fetch Cat, or give it the identifier fetch_cat/poshmark-sold-listings-scraper.
Your assistant can check the available settings and retrieve the results from the returned run. If the run is still working, it should follow that run rather than start it again. Both connection options use Apify's hosted service.
Example requests
- “Collect up to 25 sold Nike shoe listings and summarize the returned listing-price range with source links.”
- “Find up to 25 sold Coach Tabby listings and organize their available prices and sizes into a comparison table.”
- “Retrieve up to 25 sold Lululemon leggings listings and group the returned records by available size for resale research.”
These are bounded search requests. The assistant performs the summaries and comparisons after reading the dataset. Missing values are not zero, and a sample is not a complete sales history.
Normal Apify charges apply. Check the live Pricing tab before asking your assistant to run a larger batch.
Pay with x402
If your AI agent has a funded wallet, it can pay for Apify usage through x402. This experimental option lets an agent use Apify without a conventional account.
Apify AGI provides a prepaid API token with a spending cap after payment. Your agent can use that token to run this scraper through the Apify API or an authenticated MCP connection.
Some MCP setups also support paying for each request directly. That is a different payment option, so check the official guide for its availability.
Follow the official guide for wallet setup, supported payment options and current terms. Apify handles the payments. Keep wallet keys and payment tokens in your agent's secure configuration.
Other ways for agents to pay
Apify also supports MPP for prepaid access through AGI and Skyfire for eligible Actors. If your agent already uses one of these, see the agentic payment guide to choose the right setup.
FAQ
How do I search Poshmark sold listings?
Enter a keyword or supply a public search URL. The Actor requests sold listings while keeping other supplied URL filters.
Can I hide or delete sold listings?
No. This Actor only reads public search results. It cannot change your Poshmark account or listings.
Can I use it as a Poshmark sold-listings API?
You can call it using Apify's API or MCP and export the dataset. It is not an official Poshmark API and returns public search data only.
Why are fields missing or results incomplete?
Not every search result includes every optional field. Check the source search, reduce broad queries, and inspect the run summary when available. A result limit is a cap, not a guaranteed number of matches.
Related Actors
- Vinted Search Scraper — Collect public Vinted resale listings with available prices, sizes and seller fields.
- Walmart Products Scraper — Compare retail product prices.
- Shopify Products Scraper — Export public product catalogs.
- AliExpress Products Scraper — Research supplier listings.
- Craigslist Classifieds Scraper — Compare public local classified listings.
Support and feedback
For custom additions or integrations, email hello@fetchcat.dev.
Found an error or have a feature request? Open an issue with the run URL, a non-sensitive input example and what you expected.
Need help sharing it? See Apify’s guide to sharing a run when reporting an issue. Sharing a run can give the developer access to its input, logs and results, so use a run that contains no sensitive data. Please leave out API tokens, passwords, cookies, private documents and personal data. Use a public sample URL or a redacted example instead.
Tried this scraper? We'd love to hear how it worked for you. Leave a review to help others choose the right tool and help us improve it. Your feedback means a lot to us.
Made with care for curious people, AI agents and the possibilities in data. ♥