Skip to content

One API for Auction Listing Data

Auction sites mix server-rendered listings with JavaScript-driven bid panels, and they often vary content by region.

OUTPUT FORMATSHTMLJSONMarkdown

This page explains how a hosted scraping API handles those layers so your pipeline receives either rendered HTML or parsed JSON from a single auction URL.

What the API returns from an auction page

Each call takes an auction URL and returns the page after the service has rotated proxies, spoofed browser fingerprints, and rendered JavaScript where needed. The response can be raw rendered HTML for your own parser or structured JSON when you supply extraction rules.

The auction surface the API is designed to cover includes active listings, bid counts, the current high bid, seller reputation, item descriptions, photos, and time-to-close. The same call can also return seller details and closing prices when those fields are present on the page.

Three auction-data jobs and the parameters that serve them

Most auction pipelines fall into one of three jobs. The table below maps each job to the request parameters that matter most, so you can choose a starting configuration instead of enabling every option.

  • Listing collection. Use render_js=true when listing cards load after the initial HTML. Add country_code if the catalogue differs by region.
  • Bid-history collection. Bid panels are frequently JavaScript-driven, so render_js=true is usually required. Use extract_rules with CSS selectors to map bid amount, bidder label, and timestamp into named fields.
  • Price-trend analysis. Collect closing prices over time and store them with the auction end date. ai_extract_rules can describe the fields in natural language when the page markup changes often.

If a target throttles aggressive request patterns, space out calls or use multiple sessions. The API itself applies concurrency limits per plan rather than per-target rate limits.

Worked example: one auction URL to a JSON record

Suppose you want the current high bid, bid count, and closing time from a single auction page. A minimal request sends your API key and the auction URL. If the bid panel is rendered client-side, add render_js=true. To receive named fields rather than HTML, add extract_rules mapping CSS selectors to field names such as high_bid, bid_count, and closes_at.

The response returns parsed JSON with those field names. If the page markup changes, you can replace the selector map with ai_extract_rules and a natural-language description of the same fields. The API key and URL are the only required inputs; the other parameters are optional and can be added as the target requires them.

Target throttling versus API concurrency

Two different limits can slow an auction pipeline, and they need different responses.

  • API concurrency limit. Each plan caps how many requests can run at the same time. If you hit that cap, queue work or move to a plan with higher concurrency.
  • Target-side throttling. An auction site may slow or block repeated patterns from the same session. Space out requests or use multiple sessions.

The API does not impose per-target rate limits; it applies concurrency limits per plan. Treating a target-side slowdown as an API limit leads to unnecessary plan upgrades, while treating an API concurrency cap as target throttling leads to wasted retries.

Field and control map

The request parameters below are the ones the source documents for auction work. Each is optional; the API key and auction URL are the only required inputs.

  • render_js — set to true to run the page in a headless browser and return post-render HTML. Each successful request with JS rendering enabled costs 5 API credits.
  • stealth_proxy — routes the request through premium proxies for pages that challenge automated traffic. Premium proxies cost 10 or 25 API credits per successful request, depending on whether JS rendering is disabled or enabled.
  • country_code — routes through a residential IP in the named country. Geotargeting covers 200+ countries and territories, with 40+ available on classic proxies.
  • extract_rules — maps CSS selectors to field names and returns parsed JSON.
  • ai_extract_rules — describes the fields in natural language and returns parsed JSON.

API credits are valid for one month and do not roll over. Requests start at 1 credit each.

Setup and language support

Account creation gives immediate access to an API key and 1,000 free credits. The dashboard request builder lets you paste a URL, set parameters, and copy a generated snippet in Python, Node, Go, PHP, Ruby, or cURL, so you can test a request before writing pipeline code.

SDKs are published for Python, Node.js, Go, PHP, Ruby, and Java, and plain cURL works for any stack. The documentation includes examples in Python, Node.js, cURL, Java, Go, PHP, and JavaScript.

Choosing a plan for auction workloads

Plans differ in monthly API credits and concurrent requests. The plan table below preserves the published figures so you can compare credit volume against your expected request mix. Because JS rendering and premium proxies consume more credits per request, estimate the credit cost of a typical auction call before choosing a tier.

All prices are exclusive of VAT. A free trial with 1,000 credits is available without a credit card.

Published plan 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. JavaScript rendering, rotating and premium proxies, geotargeting, and screenshots and extraction rules are included on every plan. API credits are valid for one month and do not roll over; requests start at 1 credit each.

Frequently asked questions

Can I scrape Auction 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.

How do I handle JavaScript when scraping Auction?

Pass render_js=true on the request. The page runs in a real headless browser, the JavaScript executes server-side, and the post-render HTML is returned.

Can I scrape Auction from a specific country?

Yes. Pass country_code on the request to route through a residential IP in that country. This is useful when content varies by geo.

What's the rate limit for scraping Auction?

Throttling comes from two places. The API caps how many requests your plan can run at once, so queue work or move to a higher-concurrency tier when you reach that ceiling. Separately, an auction site may slow or block repeated patterns from the same session; spacing out calls or using multiple sessions addresses that. The API does not set per-target rate limits.

How do I get structured JSON from Auction?

You have two routes to parsed JSON. With extract_rules, you map CSS selectors to the field names you want. With ai_extract_rules, you describe the fields in natural language instead. Either way, the response arrives already parsed as JSON rather than raw HTML.

Which programming languages can I use to scrape Auction?

Any. SDKs are published for Python, Node.js, Go, PHP, Ruby, and Java. Plain cURL works too, so you can use whatever your stack already uses.