Malaysia's classifieds market as JSON, by category, state and town

Any combination of a keyword and a place. query is the keyword, category is a category id, slug or name such as 1020, cars or Cars, region is a state or federal territory such as selangor or Kuala Lumpur, and area is a town or district inside it, where a comma list is allowed. A bare category with no keyword browses everything in it, and a parent category id includes its children. You do not have to guess any of those ids: categories and locations are free actions that list every one.

They do here, and that is the point of the action. Mudah itself accepts a filter key it does not know and quietly returns the unfiltered set: rooms=3 left all 104,169 property ads in place, property_type, job_cat, contract_type, pet_type and gender_type did the same, and price_min with price_max went the other way and returned nothing at all. Every filter you send is resolved against mudah's own published schema first and rejected with the allowed values when it is not there. 24 filters were then run against a same-minute unfiltered control and all 24 narrowed: make=Toyota took 89,804 car ads to 19,549 and model=Hilux on top of it to 1,051 with 40 of 40 rows Hilux, condition=new took phones from 13,484 to 1,534 with 40 of 40 New, ad_type=let took property from 104,171 to 46,683 with 40 of 40 let, and seller_type private and company split 13,484 into 12,290 and 1,194 which add back to the total.

Up to 200 a call, and that ceiling is enforced because mudah does not enforce it: ask for 201 or more and it serves 24 rows with no error. Page with offset, and keep offset plus limit within 10,000, which is mudah's search window. Past it mudah reports zero total results for a category holding tens of thousands of ads, so a deeper request is refused here instead of being answered with that lie. total_results tells you how large the market really is, so partitioning by state, town, make or price band is how you reach the rest.

Mudah writes a sale price, a monthly rent and a job salary into the same field, so every row says which one it is in price_kind, reading price, rent or salary. Where an ad publishes no price at all mudah shows Negotiable, and price comes back null with price_not_published true rather than 0, because a zero there would read as free. Measured on 1,800 rows across nine categories: price is present on 40 of 40 rows in 15 of the 17 categories tested, 39 of 40 in jobs, and 0 of 40 in services, where all 200 sampled ads carried Negotiable.

For a dealer, an agency or a shop, yes, always: those are business facts, and the shop identity, its verification and its registration number where one is published come with them. For a private individual the name and number are off by default, because on a classifieds site those belong to a person. You still see that a number exists, as a masked phone_masked, and seller.pii_withheld says plainly that it was withheld rather than absent. Set include_pii to true when you have a lawful reason and the full contact comes back. Every listing also publishes seller.business_evidence, so the private-or-business call is auditable rather than a hidden rule.

No to both, and neither is invented. Mudah publishes no unit price anywhere, so there is no price per square foot on a property and no price per unit on anything else, and none is worked out here: what you get is the advertised price and, for property, the floor size, as two separate fields. There is also no sold price. Mudah stops serving an ad entirely when it goes, so a dead listing id is NOT_FOUND and there is no record of what it closed at.

Whatever the category does not publish, and it is left absent rather than guessed. listing_id, title, url, the cover image, state, town and posted_at came back on 40 of 40 rows in all 17 categories tested. Condition is not defined at all for property, jobs, services, pets, food and number plates. The vertical details block is full on cars, motorcycles, property, phones, clothes, pets and jobs, thin on business equipment at 16 of 40 and on number plates and food at 3 of 40, and empty on furniture and home appliances, which publish no extra row fields. Job ads often have no photo, 24 of 40. On the 40 listing pages measured, description and contacts were 40 of 40, images and the attribute table 38 of 40, and the specifications block 4 of 40, because only vehicles have one.

It is checked before it is reported. A genuine no-match and a throttled read look identical from the outside, both a plain empty list, so an empty search is asked a second time and only reported empty when both reads agree. The answer then carries empty_confirmed true, which means mudah really has no ad matching the query.

Mudah.my API is a ReefAPI endpoint group for malaysia's largest classifieds: cars, property for sale and to rent, phones, appliances, fashion, pets, jobs and services, priced in myr. It returns live JSON through POST requests under /mudah/v1.

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

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

Mudah.my actions currently cost 1 credit per successful call. Failed or blocked calls are free. All APIs draw from one credit pool.

Yes. Connect ReefAPI once through MCP and your assistant can call mudah actions with the same key, credit pool and JSON envelope used by normal REST requests.