Skip to content

Arabam Scraper API for Turkish Vehicle Listings

Arabam is a Turkish car-listing marketplace where dealers and private sellers publish vehicle specifications, prices, condition notes and photos.

OUTPUT FORMATSHTMLJSONMarkdown

Collecting that public inventory at scale usually means solving three problems at once: JavaScript-rendered pages, IP-based blocking, and keeping a parser in sync with layout changes. A managed scraping API moves those three concerns off your team and returns either rendered HTML or structured JSON from a single request. This page explains what the API accepts, what it returns, how credits are charged, and where the approach stops being the right tool.

What you can collect from Arabam

Public Arabam listing pages expose the details a buyer or analyst would read: make, model, year, mileage, transmission, fuel type, asking price, dealer name, location and a photo gallery. The same fields support three common workflows — building a specification dataset, tracking price movement over time, and comparing condition descriptions across similar vehicles. Because the API returns whatever renders on the public page, the practical limit is the page itself, not a fixed field list. If a value appears in the rendered DOM, it can be targeted with CSS or XPath extraction rules, or described in natural language for AI-driven extraction.

Request shape: URL in, HTML or JSON out

The core interaction is a GET request carrying the target Arabam URL and your API key. By default you receive the rendered page HTML; add extraction rules and you receive structured JSON instead. Four parameters cover most Arabam work: render_js turns on JavaScript rendering for pages that build listings client-side, stealth_proxy raises the anti-bot effort for harder targets, country_code sets the geographic origin of the request, and ai_extract_rules lets you describe the fields you want in plain language rather than writing selectors. The exact parameter names, types and requiredness are fixed in the supplied contract module and should be read there rather than inferred from prose.

How credits are charged

Every successful request consumes credits, and the amount depends on which options you enable. The published option costs are 5 credits for JavaScript rendering, 25 for premium_proxy with JS rendering, and 75 for stealth_proxy. The plan tooltips add that requests start at 1 credit each and that premium proxies cost 10 credits when JS rendering is disabled. Enabling JavaScript rendering costs 5 credits per successful request. Stealth proxy requests cost 75 credits. Credits are valid for one month and do not roll over, so a plan's monthly credit figure is a ceiling on work done that month, not a bank you can draw down later. The full plan matrix — monthly price, credit allowance, concurrency and feature inclusion — is delivered as an exact table module; read the numbers there rather than from any summary.

Worked example: costing a small monitoring job

Suppose you want to check 200 Arabam listing pages once a day and the pages need JavaScript rendering. At 5 credits per successful request, one daily pass costs 1,000 credits; a 30-day month costs roughly 30,000 credits. Against the captured reference allowance of 75,000 credits for the entry-level plan, that fits with headroom for retries and occasional stealth-proxy requests at 75 credits each; confirm the current allowance before relying on it. If you later add premium proxies with JS rendering at 25 credits, the same 200-page daily pass becomes 5,000 credits per day — 150,000 per month — which changes the plan tier you need. Run this arithmetic before choosing a tier; it is the single most common source of surprise on a scraping bill.

Three different failures, three different fixes

A failed Arabam job is rarely one problem. Distinguish them before changing anything. First, a blocked response — an anti-bot challenge or a 403 — usually means the request looked automated; try stealth_proxy or a different country_code. Second, an empty or partial extraction — the request succeeded but your selectors matched nothing — usually means the page structure changed or the content loads after your extraction point; check whether render_js is on and re-inspect the DOM. Third, credit exhaustion — requests start failing uniformly across all targets — means the monthly allowance is spent; credits do not roll over, so the fix is a plan change, not a code change. Treating all three as 'the scraper is broken' wastes the most time.

Decision checklist before you build

Use a managed API when: you need public listing data at a volume that would justify running your own headless browser fleet; you do not want to own proxy rotation and anti-bot maintenance; your team's time is better spent on analysis than on infrastructure; and your monthly volume fits a predictable credit budget. Consider self-hosted scraping instead when: you need only a handful of pages occasionally; you require a data path that never leaves your own infrastructure; or your extraction logic is so bespoke that a general-purpose renderer adds little. In every case, confirm that the pages you target are public and that your use complies with Arabam's terms and applicable law before you deploy.

Languages and setup path

The API is language-agnostic: any HTTP client works, and published SDKs cover Python, Node.js, Go, PHP, Ruby and Java. A typical setup runs in four steps — create an account and receive an API key with free trial credits, install the SDK for your stack or use plain cURL, send a request with the Arabam URL, then add advanced parameters only when a page needs them. Testing in the dashboard request builder before pasting a snippet into your codebase catches parameter mistakes early.

Compliance and data handling

Public-facing pages can usually be collected, but the target site's terms of service govern what is permitted, and post-login or personal content should be avoided. The original publisher's page states that it does not collect or store personal data from scraped sites unless the user explicitly requests it; that is the source publisher's claim, not a guarantee of this service, and the current operator's data-handling terms must be confirmed before you rely on them. Treat any such statement as a description of the operator's handling, not a substitute for your own legal review of the specific data you plan to collect and retain.

Plan comparison (captured reference)
PlanMonthly priceAPI creditsConcurrent requestsJS renderingRotating & premium proxiesGeotargetingScreenshots & extraction rulesPriority email supportDedicated account managerTeam management
Hobby$19 /mo75,00025IncludedIncludedIncludedIncludedNot includedNot includedNot included
Freelance$49 /mo250,00050IncludedIncludedIncludedIncludedNot includedNot includedNot included
Startup (Recommended)$99 /mo1,000,000100IncludedIncludedIncludedIncludedNot includedNot includedNot included
Business$249 /mo3,000,000200IncludedIncludedIncludedIncludedIncludedIncludedIncluded
Business +$599 /mo8,000,000400IncludedIncludedIncludedIncludedIncludedIncludedIncluded
Enterprise 14$999 /mo14,000,000500IncludedIncludedIncludedIncludedIncludedIncludedIncluded
Enterprise 24$1,599 /mo24,000,000600IncludedIncludedIncludedIncludedIncludedIncludedIncluded
Enterprise 41 (Recommended)$2,399 /mo41,000,000700IncludedIncludedIncludedIncludedIncludedIncludedIncluded
Enterprise 69$3,599 /mo69,000,000800IncludedIncludedIncludedIncludedIncludedIncludedIncluded
Enterprise 120$5,799 /mo120,000,000900IncludedIncludedIncludedIncludedIncludedIncludedIncluded

All prices are exclusive of VAT. Credits are valid for one month and do not roll over. Requests start at 1 credit each; JS rendering costs 5 credits, premium proxies 10 or 25 depending on JS rendering, stealth proxy 75. Plan names, prices and allowances are captured reference values and may change; confirm current terms with the provider before purchasing.

Credit cost per successful request by option
Request optionCredits per successful request
Plain request1
JavaScript rendering5
Premium proxies without JS rendering10
Premium proxies with JS rendering25
Stealth proxy75

Costs apply to successful requests. Credits are valid for one month and do not roll over.

Frequently asked questions

Do I need an Arabam account to use the scraper?

No. You only need an API key from the scraping provider. The free trial includes 1,000 credits and does not require a card. You send the public Arabam URL and the API handles rendering and proxy rotation.

Is scraping Arabam legal?

Public-facing pages are generally treated as collectable, but the target site's terms of service and applicable law govern what is permitted. Review Arabam's terms before deploying, and avoid post-login or personal content. This is general information, not legal advice.

What data can I extract from Arabam?

Anything that renders on the public page. Use extract_rules with CSS or XPath selectors, or ai_extract_rules for natural-language extraction, to receive structured JSON. Typical fields include make, model, year, mileage, transmission, fuel type, price, dealer, location and photos.

How do I start scraping Arabam?

Create an account, copy your API key, and send a GET request with the target URL. The service renders the page, rotates proxies and returns the data. The free trial gives 1,000 credits for testing.

Which programming languages can I use?

Any language with an HTTP client. Published SDKs cover Python, Node.js, Go, PHP, Ruby and Java, and plain cURL works too. Pick whatever your stack already uses.

How much does it cost to scrape Arabam?

The free trial includes 1,000 credits with no card. Paid plans start at $19/month. Per-request cost depends on options: 1 credit for a plain request, 5 for JavaScript rendering, 10 or 25 for premium proxies depending on JS rendering, and 75 for stealth proxy. Credits are valid for one month and do not roll over.