Skip to content

Scrape OfferUp Listings and Seller Details Through One API

OfferUp is a consumer-to-consumer classifieds marketplace, and its listing pages are rendered client-side, gated behind rotating IPs, and occasionally defended with CAPTCHA challenges.

OUTPUT FORMATSHTMLJSONMarkdown

This page describes a hosted scraping API that accepts an OfferUp URL plus your extraction logic and returns either structured JSON or the post-render HTML. You do not run headless Chrome, rotate proxies, or maintain fingerprint spoofing yourself. Below you will find the fields a listing response carries, the request parameters that control rendering and stealth, a credit-cost checklist for sizing a plan, and the failure modes worth distinguishing before you build.

What a single OfferUp request returns

One call takes an OfferUp listing URL and returns the page content after JavaScript has executed. The documented field set covers title, asking price, condition, location, posting date, seller name and rating, and the full image gallery. Output format is your choice: structured JSON when you supply extraction rules, or the rendered HTML when you want to parse it yourself.

A practical way to think about the response is in three layers. The listing layer holds the item facts — title, price, condition, location, posting date. The seller layer holds the name and rating attached to the account behind the listing. The media layer holds the image gallery. If your pipeline only needs the listing layer, you can keep extraction rules narrow and reduce parsing work downstream.

Field map and typical use

Use this as a planning aid when you decide which fields to extract and which to leave out.

  • Title — item identification and keyword matching across categories.
  • Asking price — price-drop detection and market-range comparisons.
  • Condition — filtering new versus used inventory before analysis.
  • Location — geographic segmentation of listings.
  • Posting date — time-on-market calculation and listing age.
  • Seller name — grouping listings by account.
  • Seller rating — weighting or filtering sellers by reputation signal.
  • Image gallery — visual review, deduplication, or thumbnail capture.

If you need a field that is not in this list, the answer depends on whether it renders on the public page. Anything visible in the public HTML after JavaScript runs can be targeted with CSS or XPath extraction rules, or with AI-driven extraction rules that return structured JSON.

Request parameters that change the outcome

Four parameters cover most OfferUp scenarios.

  • render_js — set to true when the page needs JavaScript execution. The page runs in a real headless browser server-side, and you receive the post-render HTML.
  • stealth_proxy — enable this when a target responds aggressively to normal traffic. It routes the request through a stealthier proxy path.
  • country_code — routes the request through a specific country or territory when geotargeting matters.
  • ai_extract_rules — describes the fields you want in natural language and returns structured JSON instead of raw HTML.

A fifth option, extract_rules, takes CSS or XPath selectors when you already know the page structure and want deterministic extraction rather than AI inference. Choose extract_rules for stable layouts and ai_extract_rules when the layout shifts or you are prototyping.

Three workflows that come up repeatedly

Product-detail collection. Pull title, price, condition, location, seller details and images from individual listing pages to build a market-research or competitor dataset.

Seller listing statistics. Group listings by seller name and rating to evaluate engagement signals and support lead-generation or business-development research. This works at the aggregate level; there is no per-user transaction access.

Listing change tracking. Re-request the same listing URLs on a schedule and compare asking price, posting date and seller across snapshots. This surfaces price drops, time on market, and seller-listing patterns.

A concrete example: keep a table keyed by listing URL with columns for last seen price, first seen posting date, and seller name. On each run, fetch the listing, compare the new asking price to the stored value, and write a row only when the price changed or the posting date is new. That gives you a price-drop log without storing every unchanged snapshot.

Distinguishing the three failure modes

Not every failed request means the same thing, and the fix differs.

  1. IP-based blocking. The response looks like a block page or an empty body. Rotating residential proxies and a real headless browser make requests resemble normal traffic; if the target is aggressive, enable stealth_proxy on the request.
  1. JavaScript-only content. The HTML comes back but the listing fields are missing because the page had not finished rendering. Set render_js=true so the page executes in a real headless browser before the HTML is returned.
  1. CAPTCHA challenge. The response contains a challenge instead of the listing. The stealth_proxy parameter is the documented lever for this case.

If you see a block page after enabling stealth_proxy, the issue is more likely the target's rate policy than your request configuration. Slow the schedule before adding more retries.

Credit-cost checklist before you pick a plan

Credits are consumed per request, and the cost depends on which features you enable. Use this checklist to estimate monthly volume before comparing tiers.

  • Base request: 1 credit.
  • JavaScript rendering enabled: 5 credits per successful request.
  • Premium proxies with JS rendering disabled: 10 credits per successful request.
  • Premium proxies with JS rendering enabled: 25 credits per successful request.
  • API credits are valid for one month and do not roll over.
  • Concurrent requests are the number of requests that can be sent at the same time.

Worked estimate: 1,000 OfferUp listing requests per month with JS rendering and premium proxies enabled would cost 25,000 credits. That fits comfortably inside the Hobby tier's 75,000 credits, but leaves little headroom for retries or a second workflow. If you plan to run both a detail workflow and a change-tracking workflow, size the plan against the combined request count, not just one of them.

Plan tiers differ in credits, concurrency, and support features. The pricing table on this page lists the exact credit allowances and concurrency limits for each tier; check current pricing before committing because tiers and allowances can change.

Getting from zero to a first request

The documented path is four steps. Create an account to receive an API key and starting credits. Install a client library if you want one — Python, Node.js, Go, PHP, Ruby and Java are all documented, and raw cURL works too. Send a single HTTP request containing your API key and an OfferUp URL. Add advanced parameters only when the page needs them.

If you prefer not to write code at all, the dashboard request builder lets you paste a URL, set parameters, and copy a generated snippet in any of the supported languages or cURL. That snippet can be dropped into a script or an automation workflow such as n8n.

Legality and scope

Public-facing pages can usually be scraped, but the target site's terms of service should be reviewed before deploying, and post-login content should be avoided. This page describes extraction from public listing pages only. Seller statistics are aggregate-level signals; there is no per-user transaction access.

Plan credit and concurrency comparison
PlanMonthly priceAPI creditsConcurrent requestsPriority email supportDedicated account managerTeam management
Hobby$19 /mo75,00025Not includedNot includedNot included
Freelance$49 /mo250,00050Not includedNot includedNot included
Startup (Recommended)$99 /mo1,000,000100Not includedNot includedNot included
Business$249 /mo3,000,000200IncludedIncludedIncluded
Business +$599 /mo8,000,000400IncludedIncludedIncluded
Enterprise 14$999 /mo14,000,000500IncludedIncludedIncluded
Enterprise 24$1,599 /mo24,000,000600IncludedIncludedIncluded
Enterprise 41 (Recommended)$2,399 /mo41,000,000700IncludedIncludedIncluded
Enterprise 69$3,599 /mo69,000,000800IncludedIncludedIncluded
Enterprise 120$5,799 /mo120,000,000900IncludedIncludedIncluded

All prices are exclusive of VAT. All tiers include JavaScript rendering, rotating and premium proxies, geotargeting, and screenshots and extraction rules. Plan names, credit allowances and concurrency limits are captured reference figures; verify current pricing before purchase.

Frequently asked questions

Is scraping OfferUp legal?

Pages that are open to the public are generally fair game for collection, yet you should still read OfferUp's terms of service before you deploy anything, and stay away from anything behind a login. This page covers public listing pages only.

What data can I extract from OfferUp?

Whatever the public page renders is available. Pass extract_rules with CSS selectors, or ai_extract_rules to let AI handle extraction, and you get structured JSON back. The documented listing fields are title, asking price, condition, location, posting date, seller name and rating, and the full image gallery.

How do I start scraping OfferUp?

Sign up, grab your API key, and send a GET request with the target URL. The service renders the page, rotates proxies, and returns the data. Starting credits are included so you can test before committing to a plan.

Will I get blocked when scraping OfferUp?

Residential proxies rotate and a real headless browser is used, so requests resemble normal traffic. If a target gets aggressive, enable stealth_proxy on the request. If blocking persists after that, slow your schedule before adding retries.

Can I scrape OfferUp without writing code?

Yes. The dashboard request builder lets you paste a URL, set parameters, and copy the generated snippet in Python, Node, Go, PHP, Ruby, or cURL. That snippet can also be used inside an automation workflow such as n8n.

How do I handle JavaScript when scraping OfferUp?

Pass render_js=true on the request. The page runs in a real headless browser, the JavaScript executes server-side, and you receive the post-render HTML. Note that enabling JS rendering raises the credit cost per successful request.

How many credits does one OfferUp request cost?

A base request costs 1 credit. Enabling JavaScript rendering raises the cost to 5 credits per successful request. Enabling premium proxies costs 10 credits without JS rendering, or 25 credits with JS rendering enabled. API credits are valid for one month and do not roll over.

What format does the response come in?

Either structured JSON when you supply extraction rules, or the rendered HTML when you want to parse it yourself. AI-driven extraction rules return structured JSON without you writing selectors.