Skip to content
Scrappa Get API key
Mudah.my Property API 1 credit/request

Mudah.my Property Count API Documentation

GET https://scrappa.co/api/mudah-property/v1/count

Mudah.my Property Count API returns the number of listings for the same filters as search, without loading the listings. The response also splits the count into agent and private owner listings. Use it for market statistics, filter previews and monitoring.

Mudah.my Property Count API Documentation 1 credit/request

Endpoint

Request preview
GET
https://scrappa.co/api/mudah-property/v1/count
Auth header
x-api-key
Cost
1 credit/request
Response preview
200 OK
{
    "data": {
        "total": 20051,
        "by_seller_type": {
            "agent": 18010,
            "private": 2041
        },
        "search_parameters": {
            "region": 8,
            "category": "apartment",
            "listing_type": "sale"
        }
    },
    "meta": {
...

Parameters

Start with the required fields, then add optional filters only when your use case needs them.

Runnable path

This endpoint has no required query parameters.

16 optional filters available.

listing_type string Optional

sale (default) or rent. Example: rent.

Example value example
category string Optional

residential (default), all, apartment, house, commercial, land or room (room needs rent). Example: apartment.

Example value example
region integer Optional

State id from autocomplete or the reference route. Example: 8 for Selangor.

Example value US
subarea integer Optional

Subarea id from autocomplete. Example: 353.

Example value 10
building_id string Optional

Building UUID from autocomplete or the buildings route.

Example value 1234567890
q string Optional

Free text keyword, 2 to 100 characters. Example: freehold.

Example value coffee shops
bedrooms integer Optional

Bedrooms 1 to 5. 5 means 5 or more. Example: 3.

Example value 10
bathrooms integer Optional

Bathrooms 1 to 5. 5 means 5 or more. Example: 2.

Example value 10
property_type_id integer Optional

Property type id from the reference route. Example: 1 for condominium.

Example value 1234567890
furnished_id integer Optional

Rent only. 1 fully, 2 partially, 3 not furnished. Example: 1.

Example value 1234567890
min_price integer Optional

Minimum price in MYR (rent: per month). Example: 300000.

Example value 10
max_price integer Optional

Maximum price in MYR (rent: per month). Example: 500000.

Example value 10
min_size integer Optional

Minimum built-up size in sq.ft. Example: 800.

Example value 10
max_size integer Optional

Maximum built-up size in sq.ft. Example: 1500.

Example value 10
store integer Optional

Seller store id. Example: 790734.

Example value 10
user_id integer Optional

Seller user id. Example: 6690932.

Example value 1234567890

Response Schema

Example response fields are illustrative; inspect the JSON before integrating.

Example response fields

Scan these fields before integrating.

data meta success
JSON Response
200 OK
{
    "data": {
        "total": 20051,
        "by_seller_type": {
            "agent": 18010,
            "private": 2041
        },
        "search_parameters": {
            "region": 8,
            "category": "apartment",
            "listing_type": "sale"
        }
    },
    "meta": {
        "billable": true,
        "endpoint_family": "count"
    },
    "success": true
}

Errors

Handle these documented responses before retrying or showing customer-facing failures.

422

Validation Error

A required parameter or a value is invalid. This response is not billable.

{
    "errors": {
        "field": [
            "The field is invalid."
        ]
    },
    "message": "The request validation failed"
}
503

Upstream Unavailable

Mudah.my could not be reached. This response is not billable and is retryable.

{
    "meta": {
        "billable": false,
        "retryable": true,
        "endpoint_family": "count"
    },
    "error": {
        "code": "UPSTREAM_UNAVAILABLE",
        "message": "Mudah.my could not be reached. Please retry shortly."
    },
    "success": false
}
503

Unexpected Upstream Data

Mudah.my returned data in an unexpected shape. This response is not billable and is retryable.

{
    "meta": {
        "billable": false,
        "retryable": true,
        "endpoint_family": "count"
    },
    "error": {
        "code": "INVALID_UPSTREAM_SHAPE",
        "message": "Mudah.my returned data in an unexpected shape. Please retry shortly."
    },
    "success": false
}

Generate Code with AI

Copy a ready-made prompt with all the endpoint details, parameters, and example responses. Paste it into ChatGPT, Claude, or any AI assistant to instantly generate working code.

Try It Live

Test this endpoint in our interactive playground with real data.