Get Saudi car listings, SAR prices and full specs from Syarah with one API

Yes, and it works on both language surfaces. A search for تويوتا returned the same 672 Toyotas as the English word toyota, and كامري, لاندكروزر and برادو all resolve through the suggest action. You can also set the response language, which switches the make, model, colour, fuel and gearbox labels to Arabic. One honest note: a few trim names come back in Arabic even on the English surface, because that is how Syarah stores them - we return the stored value rather than inventing a translation.

All of them. This is the unusual part of Syarah compared with other car marketplaces: there is no paging ceiling. A 3,674-car query reports 37 pages of 100, the last page returns exactly 74 rows so the arithmetic closes, and asking for page 38 or page 999 returns an empty list rather than quietly serving page 37 again. A full walk of a 109-car query handed back 109 unique listing ids. Pages are up to 100 rows; Syarah itself refuses more than that and says so.

Yes, and it is worth saying because on most classifieds sites it is not. Sorting by newest uses Syarah's own first-activation order: on one measured page, all twelve rows had been listed the previous day, with a lot age of nought or one day, while the site's default order mixed cars that were three to eighty-three days old. The detail call returns that date as listed_at along with days_on_lot. The one limitation: search rows carry no date field - Syarah does not publish one there - so you get the order from search and the date from detail or batch.

SAR, and the API reads it back out of Syarah's own response on every call instead of writing it in. Price integrity was checked against four independent numbers in the same payload - the search row, the listing's own price block, its analytics record and the schema.org data on the page itself - and all four agreed on ten of ten listings sampled across new, used, GCC-spec, hybrid and 200,000-SAR-plus stock. Two separate fields are returned where a car is discounted: discount is the cut, and price_before_discount is the pre-cut price, so you never have to guess which is which.

No, and we would rather say so than ship a box that does nothing. Syarah accepts no location parameter: every spelling we tried returned the complete unfiltered catalogue. The city is returned on every row, so you can filter it yourself - across 278 measured rows it was Riyadh 141 times, Al Qurayyat 90, Jeddah 40 and Dammam 7. If you mainly want Riyadh, filtering to Syarah's own inspected stock gets you close, since that inventory sits there. Send a city parameter anyway and the response explains why it cannot work.

It tells you what kind of seller it is: Syarah itself, a dealer on the platform, or a private owner. Syarah's own inspected inventory was 1,769 of the 3,674 cars and dealer or private stock the other 1,905 - the two add up exactly. Syarah sells centrally rather than putting sellers in touch with buyers, so there is no per-listing phone number or seller profile on the public page, and none is returned.

The spec card, the equipment list, the whole gallery and the listing date. Across twelve listings, detail returned twenty-one to sixty-two individual features grouped into safety, comfort, technology and exterior, and fourteen to thirty-seven photos - against a five-image preview on a search row. It also adds cylinders, engine type, gear count, doors, key count, both colour hex codes, the financing breakdown and the warranty, plus listed_at and days_on_lot. Horsepower, fuel-tank size, gear count and door count only appear on part of the stock, so they are returned where Syarah publishes them and left empty where it does not.

Every filter was measured against an unfiltered control of 3,674 cars in the same run, and all twenty bit: under 40,000 SAR cut it to 638, under 20,000 km to 1,128, model year 2025-2026 to 1,304, electric to 11, pickups to 109. One quirk we handle for you: Syarah silently ignores a range that only has one end, so if you send just a maximum price the API supplies the other end itself and tells you it did. One quirk to know about: an instalment range also drops the 1,218 cars that carry no instalment at all.

Use batch. It takes up to 100 listing ids and returns their current rows in a single request, which was measured working at exactly 100 ids. Ids that Syarah no longer publishes come back in a missing_ids list, so a sold or withdrawn car is visible instead of silently absent from the answer. Compared with calling detail a hundred times it is one request instead of a hundred, and priced accordingly.

VIN, service history, previous-owner count, view counts and seller contact details are not on the public listing, so they are not in the response - absent rather than guessed. The listing page does print a VIN field, but it is seventeen zeros on every car, so we do not return it at all. Brand-new cars carry no odometer reading, which the API returns as empty rather than as zero - that was true on ninety-three of ninety-three new rows measured. And cylinders and cabin count, which search rows leave empty on every row, are returned by detail instead.

Syarah API is a ReefAPI endpoint group for saudi arabia's online car marketplace: used and new stock from syarah's own inspected inventory, dealers and private sellers, priced in sar, searchable in arabic or english. It returns live JSON through POST requests under /syarah/v1.

Yes. ReefAPI starts with 1,000 free credits, no card required. Syarah calls use the same shared credit balance as every other ReefAPI engine.

No login to Syarah 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.

The page example is captured from a live search call, and production requests fetch live data through ReefAPI rather than a static sample.