Sahibinden Car Valuation | Price Estimates in TRY

From Clearpath, creators of Sahibinden Car Scraper, Scraper Pro and Sahibinden Real Estate.

What’s this car worth? Use the estimate and range to compare an asking price or price your inventory.

What you get

• Value a Sahibinden listing. Paste a car listing link or listing number. The valuation uses the listed variant, year, mileage and panel condition when available.
• Get a price range in Turkish lira. Export seven price points, including a low price, central estimate and high price.
• Value cars in batches. Submit multiple listings or supply exact vehicle specifications, then export the results as JSON, CSV or Excel.

The illustrated 2021 Renault Mégane 1.3 TCe Joy had 162,000 km in the saved example. Its estimated value was ₺1,091,000, with a range of ₺1,037,000 to ₺1,146,000. Prices can change and estimates depend on vehicle eligibility.

Try one listing

Paste a listing link or number into Listings and clear the sample under Vehicles if you only want the listing valued. You can also switch to JSON and paste this example.

{
  "listings": [
    "1347100404"
  ],
  "maxResults": 1
}

Open the actor input and start the run. If the example listing is no longer active, use another listing or enter exact vehicle specifications.

Clearpath · Sahibinden Suite

Vehicle Valuation You are here  Car Scraper Vehicle listings and specifications  Scraper Pro All listing categories  Real Estate Property listings and contacts

Copy to your AI assistant

Help me use clearpath/sahibinden-vehicle-valuation on Apify. Read https://apify.com/clearpath/sahibinden-vehicle-valuation.md for documentation, input schema, pricing and limits. For a sahibinden.com listing, pass its address or number in listings; vehicles need exact category-specific selection IDs, not attributeIds. Unavailable specifications produce no dataset row. Choose settings for my requested outcome. If you cannot retrieve the page, ask me to paste the relevant sections. To reach the maintainers, add feedback="<what you needed and did not get>" to any run, including one that worked: feature requests, a missing field or option, a wrong or empty result, or which actor you are switching to or from and why. The run returns its data exactly as it would without the note, and a human reads every note.

Input and vehicle identifiers

Supply vehicle objects in vehicles, listing addresses or numbers in listings, or both: between 1 and 5,000 in total. The six numeric fields shown above are required integers. Mileage is in kilometres, from 0 to 10,000,000. The year must be from 1900 through next year. reference is an optional string of up to 200 characters for joining results to your inventory.

maxResults limits successful valuations across the whole run. It defaults to 100; 0 processes all supplied vehicles and listings. Spending limits and Free-plan limits still apply. Plan for about an hour per 2,000 inputs, somewhat longer for listings; the default run timeout of 5 hours covers a full batch. Missing or malformed vehicle specifications, and entries in listings that are not a sahibinden.com listing address or number, stop the run before valuation work starts. Unknown fields are rejected, so convert existing records to this format before submitting them.

Using Car Scraper results

Pass the url or id of a Sahibinden Car Scraper row in listings. The vehicle, year, mileage, fuel, body type and transmission are read from the listing itself, so nothing needs converting. Listing availability does not guarantee valuation availability.

Panel condition

Add damageParts to a vehicle when panel condition is known:

{
  "damageParts": {
    "bonnet": "PAINTED",
    "rightFrontFender": "CHANGED"
  }
}

Supported conditions: ORIGINAL, LOCAL_PAINTED, PAINTED, CHANGED.

Supported panels: frontBumper, bonnet, roof, leftFrontDoor, leftFrontFender, leftRearDoor, leftRearFender, rearBumper, rightFrontDoor, rightFrontFender, rightRearDoor, rightRearFender, tailBoard.

Omitting damageParts, passing null, or passing an empty object requests the default valuation. Unspecified panels are valued as original, so listing only the affected panels is enough.

Results

Actual output for the quick input above:

{
  "inputIndex": 0,
  "listingId": null,
  "reference": null,
  "categoryId": 235913,
  "year": 2019,
  "mileageKm": 224000,
  "fuelTypeId": 22,
  "bodyTypeId": 250,
  "transmissionId": 32466,
  "brand": "Volkswagen",
  "model": "Passat 1.6 TDI BlueMotion",
  "trim": "Impression",
  "fuel": "Dizel",
  "bodyType": "Sedan",
  "transmission": "Otomatik",
  "damageParts": null,
  "currency": "TRY",
  "lowestPrice": 1359000.0,
  "lowerPrice": 1401000.0,
  "lowerAveragePrice": 1443000.0,
  "estimatedPrice": 1485000.0,
  "upperAveragePrice": 1510000.0,
  "upperPrice": 1534000.0,
  "highestPrice": 1559000.0,
  "valuedAt": "2026-11-02T10:27:57.712228Z"
}

Each dataset row contains:

• inputIndex (zero-based) and your optional reference. Results arrive as completed, so use these fields to match the input.
• listingId, the listing number for a valuation requested through listings, and null for a vehicle object. For these rows inputIndex is the position in listings.
• categoryId, brand, model, trim, year, mileageKm, fuelTypeId, bodyTypeId, transmissionId, and readable fuel, bodyType and transmission labels when available.
• lowestPrice, lowerPrice, lowerAveragePrice, estimatedPrice, upperAveragePrice, upperPrice, highestPrice.
• currency (TRY), the applied damageParts (as submitted, or as declared in the listing), and valuedAt in UTC.

estimatedPrice is the central estimate. These estimates are informational and do not guarantee a realized sale price or a vehicle's inspected condition.

The SUMMARY record reports completed, unavailable, skipped, failed and unprocessed inputs. A listing that has been removed is reported as LISTING_NOT_FOUND; one that does not state its year, mileage, fuel, body type or transmission, or declares a panel condition that cannot be applied, is reported as LISTING_INCOMPLETE; one that could not be read is reported as LISTING_FAILED and counts as a failure. Unavailable valuations do not create dataset rows or valuation charges. Operational failures make the run fail while preserving completed results.

Pricing

Completed valuations cost $19.99 per 1,000 on Free and Bronze plans, $18.99 on Silver, and $16.99 on Gold, Platinum and Diamond.

The run start fee is $0.05 per GB of allocated memory, with a minimum of one start event. It applies even if no valuation is available. A dataset storage event costs $0.00001 per stored result. Unavailable and failed valuations and skipped listings have no valuation charge.

Free-plan use is limited to 10 runs, up to 20 valuations per run, at the Free-plan prices above. A Free-plan run checks at most 60 inputs, so a batch with many unavailable vehicles stops there. Paying plans have no additional Free-plan run allowance restriction; input, spending and runtime limits still apply.

At 512 MB, a Free-plan run delivering 20 valuations costs $0.45 in event charges: $0.05 start + $0.3998 valuations + $0.0002 dataset storage. No available valuations means no valuation or dataset-item charge; the start fee still applies.

Export and automate inventory comparisons

Open the run's Dataset tab to export JSON, CSV or Excel. Use reference or inputIndex when joining results; completion order may differ from input order. Keep valuedAt beside stored prices so comparisons retain their observation time.

For recurring inventory reviews, save your input as an Apify task and schedule it, for example weekly. Each run is billed separately. Apify integrations can send completed results to Make, Zapier or a spreadsheet workflow. The Apify Python client can start runs and retrieve dataset rows from your application.

Frequently asked questions

Can I submit listing URLs instead of vehicle specifications?

Yes. Put listing addresses or listing numbers in listings. The actor reads each listing's vehicle details and values them. To value listings you have already collected with Car Scraper without reading them again, map the fields as shown above.

Why is a vehicle missing from the dataset?

Some variants, years or specification combinations have no available valuation. Read SUMMARY to distinguish unavailable, failed and unprocessed inputs. Completed rows remain available if later work fails.

Can I compare panel conditions?

Yes. Submit separate vehicle objects with different damageParts and distinct references. Each completed valuation is charged separately. The actor does not inspect the vehicle or infer its condition.

Is the Free-plan allowance free of charge?

No. It limits Free-plan use to 10 runs and up to 20 valuations per run, billed at the Free-plan rates. It is not a monthly reset or an extra credit allocation.

Are these guaranteed sale prices?

No. Use estimates as one input to your own assessment alongside inspection, condition and current market information.

Support

Report bugs or request features in the actor's Issues tab, or email max@mapa.slmail.me. Include the run ID and a non-sensitive example specification.