Get otoplus's inspected used cars in Turkey with price, VIN and expertise report in one API
The otoplus API returns the used cars that otoplus sells from its own stock in Turkey as clean JSON in three actions.
3 active endpoints, on 2 and 3 credit tiers.
- POST/otoplus/v1/search
- POST/otoplus/v1/detail
- POST/otoplus/v1/makes
What otoplus endpoints does ReefAPI ship?
3 live read endpoints. Read-only data API: no writes, no account actions, no dashboard access on the target site.
otoplus API
2 of 3 endpoints, ready to run
Filter otoplus's stock and get 12 cars a page with asking price, special price, credit offer, mileage, VIN, sales centre and photos, plus otoplus's own total and make counts.
// Press "Try it" and this pane shows exactly what the // live site returned this second — including an empty // result, if that is the truth. No key, no account.
How the otoplus API works
otoplus is a normal ReefAPI surface — the same four rules that hold for every other engine on the key.
No OAuth app, no request signing, no per-site account. One key covers all 438 engines.
Every route is a POST with a JSON body. Parameters are validated against the published schema before anything is charged.
Credits, not seats. Failed and blocked calls are never charged, and cache hits cost nothing.
One envelope everywhere. meta carries latency_ms, record_count and the endpoint that answered.
Find unpainted SUVs under 1.5 million lira in İstanbul
otoplus inspects every car, so you can shortlist by price and then keep only the cars whose expertise report shows no painted or replaced panel.
Each row carries price, mileage, model year, VIN and the sales centre.
12 cars a page; a page past the last returns no rows.
expertise.summary gives painted and replaced counts; body_panels names each panel.
A price-ranked list of İstanbul SUVs with every panel original, each with plate, VIN, warranty and the sales centre's phone.
curl -X POST https://api.reefapi.com/otoplus/v1/search \
-H "x-api-key: $REEF_KEY" \
-H "content-type: application/json" \
-d '{"make":"peugeot","sort":"price_asc"}'{
"ok": true,
"data": { … },
"meta": {
"api": "otoplus",
"endpoint": "search",
"mode": "live",
"latency_ms": …,
"record_count": …
},
"error": null
}The price and condition fields otoplus publishes on each car
An otoplus listing carries several money figures and a full expertise report. The API returns each under its own name; the examples are two cars measured on 2026-10-07.
| Field | What it is | Example |
|---|---|---|
| price_try | Asking price shown on the card and the vehicle page | 2,040,000 TRY (2025 Skoda Octavia) |
| special_price_try | The site's 'Size Özel' price, where otoplus shows one | Present on 72 of 139 cars |
| credit_offer | The 'Kredi Fırsatı' block: amount, term, monthly interest and the site's own text | 329,000 TRY, 11 months, 0.99 % |
| consultancy_fee_try | Consultancy fee the page says the buyer pays | 7,500 TRY |
| motor_vehicle_tax_try | Current and next motor vehicle tax (MTV) instalment | 647 / 647 TRY |
| expertise.summary | Body panels checked, and how many are original, painted or replaced | 13 checked: 11 original, 2 painted, 0 replaced |
| plate_number / vin | Number plate and 17-character VIN | plate as printed / 17-character VIN |
otoplus gives a valid 17-character VIN for 112 of 139 cars. For the rest its VIN field holds an internal code or a mistyped value (for example the letter O typed for a zero); vin is then null and the source's own string is kept in vin_as_published, so nobody keys a database on a value that is not a VIN.
What was measured on 2026-10-07
Two live runs on the same code, each walking otoplus's whole stock page by page, running 28 filtered searches against an unfiltered one and opening 8 cars of 8 different makes in full.
Turkey, prices in TRY; sales centres in İstanbul, Ankara and İzmir
139 cars in the first run and 138 in the second, across 21 makes, all sold by otoplus itself
12, with otoplus's own total; 139 cars over 12 pages, no repeats
Asking price matched the site's schema.org price and the price in the car's own URL on 139 of 139 cars
8 of 8 cars matched their search row on id, price, mileage, year, make and VIN
13 body panels on 8 of 8 cars opened
Median 1.2 to 1.5 seconds for search and 0.8 to 1.0 seconds for detail; the slowest of 118 successful calls took 2.2 seconds
Accident and service history, owner count; engine power and consumption filled on 1 of 9 cars checked
What people build with otoplus
The jobs this data is most often used for.
endpoints
credits per call
Used-car dealers in Turkey price their own stock against an inspected, fixed-price retailer's live asking prices by make, model, year and mileage.
Car-loan and leasing teams read the credit offer, credit limit and instalment options otoplus quotes for each car.
Insurers and valuation tools pull the panel-by-panel expertise report - original, painted or replaced - together with plate number and VIN.
Market analysts track how many cars otoplus holds per make, city and fuel type, and how its asking prices move over time.
What otoplus data costs
The cheapest call here is 2 credits, so $15/mo (Pro) buys 5,000 of them — $1.50 per 1,000 credits. Credits roll over and never expire, and failed or blocked calls are not charged.
Full pricing →- 1,000 free credits on signup, no card
- One key, all 438 APIs, one credit pool
- Failed and blocked calls are never charged
- Credits roll over and never expire
Call it in two lines
Sign up, get 1,000 credits and one key that works on every engine. Then this is the whole protocol.
curl -X POST https://api.reefapi.com/otoplus/v1/search \
-H "x-api-key: $REEF_KEY" \
-H "content-type: application/json" \
-d '{"make":"peugeot","sort":"price_asc"}'import requests
r = requests.post(
"https://api.reefapi.com/otoplus/v1/search",
headers={"x-api-key": REEF_KEY},
json={
"make": "peugeot",
"sort": "price_asc"
},
)
print(r.json()["data"])Have a question? We got answers.
The questions people actually ask before wiring up otoplus.
Get a free key →What does the otoplus API cover?▾
The used cars otoplus sells from its own stock in Turkey, held at its sales centres in İstanbul, Ankara and İzmir. On 2026-10-07 that was 138 to 140 cars across 21 makes (İstanbul 57, Ankara 45, İzmir 38). The stock is small and moves: the count went from 140 to 139 to 138 within half an hour.
Who is the seller?▾
otoplus itself on every car. There are no private sellers or third-party dealers. Each car names the otoplus sales centre that holds it with its address; detail adds the centre's phone number.
Does it return the expertise report?▾
Yes, on detail. All 8 cars opened on 2026-10-07 carried 13 body panels, each marked original, painted or replaced with otoplus's Turkish label, plus a summary count; some cars also carry mechanical checks such as oil or water leaks. Of those 8 cars, 6 had at least one painted panel and none had a replaced panel.
Are reserved or sold cars included?▾
Sold cars disappear from otoplus and its sitemap, and opening a sold car's id returns NOT_FOUND. Every row carries status and reserved for cars on hold; none of the 139 cars was reserved on 2026-10-07.
Do the filters really filter?▾
Each was compared with an unfiltered search in the same run (139 cars): make peugeot 23, peugeot 3008 9, İstanbul 57, diesel 34, hybrid 16, manual 14, SUV 65, sedan 27, kombi 15, credit campaign 102, from 2,000,000 TRY 23, up to 1,200,000 TRY 22, model year 2024 or newer 63, up to 30,000 km 45, query clio 5, and inside Renault (16): İzmir 5, hybrid 1. Every returned row matched its filter. Values otoplus would silently ignore are refused instead.
How many results can one search return?▾
12 cars a page, with otoplus's own total, last_page and has_more. A page past the last one comes back empty instead of repeating the last page.
How do I open one car in full?▾
Take id from a search row (for example 575530) and call detail with it, or pass the car's otoplus URL. A car that is no longer on sale returns NOT_FOUND.
What does otoplus not publish?▾
Accident or insurance-claim history, service records and the number of previous owners are not on these pages. Engine power, fuel consumption and dimensions are filled in otoplus's own data on only 1 of 9 cars checked, so on most cars those specs fields come back null; segment and engine displacement were present on 9 of 9. otoplus has no model-year or mileage sort.
What is the otoplus API?▾
otoplus API is a ReefAPI endpoint group for turkey's inspected used cars from otoplus as json: price, credit offer, plate, vin, warranty and the full panel-by-panel expertise report. It returns live JSON through POST requests under /otoplus/v1.
Is the otoplus API free to try?▾
Yes. ReefAPI starts with 1,000 free credits, no card required. otoplus calls use the same shared credit balance as every other ReefAPI engine.
Do I need an otoplus login or account?▾
No login to otoplus is needed for the API response. You call ReefAPI with your x-api-key header, and the playground can run live examples before you create a production key.
How fresh is the otoplus data?▾
The page example is captured from a live search call, and production requests fetch live data through ReefAPI rather than a static sample.
How many credits does the otoplus API use?▾
otoplus actions currently cost 2-3 credits per successful call. Failed or blocked calls are free. All APIs draw from one credit pool.
Can I call otoplus from an AI assistant or MCP client?▾
Yes. Connect ReefAPI once through MCP and your assistant can call otoplus actions with the same key, credit pool and JSON envelope used by normal REST requests.
99 Classifieds & Second-hand APIs on the same key
One key, one credit pool, one response envelope. If you are pulling otoplus, you are one call away from the rest of the category — no second contract, no second integration.
Need something this API does not do?
Name the endpoint, the field, or a source we do not carry yet. We ship new APIs every week and you would be first to get the key. Real people read every message and reply the same day.
Try it on your own data before you pay anything
The call above is the real endpoint, not a recording. A free key gives you 1,000 credits, the other 437 APIs, and the same envelope everywhere.
Endpoints, parameters and credit costs on this page are read from the live catalog and cannot drift from what the API accepts. Field notes were captured on 2026-10-07.