API Documentation

Introduction

UAEPropertyAPI provides RESTful endpoints for accessing UAE real estate data. All responses are JSON. Whether you are building a property search portal, a market analytics dashboard, or an agent directory, UAEPropertyAPI gives you access to hundreds of thousands of listings, agent profiles, agency data, and more.

Prefer to try the endpoints in a client first? The full Property Finder API collection is on Postman: fork it from the public workspace and paste your RapidAPI key. Python and JavaScript examples are on GitHub.

Need Bayut and Property Finder through one key? That is a separate API, the UAE Real Estate API, with its own documentation page.

Base URL

All API requests should be made to the following base URL:

Authentication

UAEPropertyAPI is hosted on RapidAPI. Every request must include two authentication headers:

• x-rapidapi-key — Your unique API key from RapidAPI.
• x-rapidapi-host — Must be set to uae-real-estate-property.p.rapidapi.com.

{
  "x-rapidapi-key": "YOUR_API_KEY",
  "x-rapidapi-host": "uae-real-estate-property.p.rapidapi.com"
}

Rate Limits

Rate limits depend on your RapidAPI subscription plan. The free tier includes a limited number of requests per month, while paid plans offer higher quotas and faster response times. Check your RapidAPI dashboard for your current plan limits and usage. If you exceed your rate limit, the API will return a 429 Too Many Requests response.

Response Format

All responses are returned as JSON. Successful listing searches follow this structure, with total_count for pagination (about 38 results per page; page starts at 1):

{
  "success": true,
  "total_count": 5752,
  "data": [
    {
      "property_id": "166080417",
      "property_type": "Apartment",
      "price": { "value": 70000, "currency": "AED", "period": "yearly" },
      "bedrooms": "studio",
      "bathrooms": "1",
      "size": { "value": 476, "unit": "sqft" },
      ...
    },
    ...
  ]
}

Endpoints

Error Handling

When an error occurs, the API returns a JSON response with "success": false, and an error field. Validation errors (400) list each invalid parameter under error.issues. Always check the HTTP status code and handle errors gracefully in your application.

// 400 Bad Request (validation error)
{
  "success": false,
  "error": {
    "issues": [
      { "code": "invalid_type", "path": ["location_id"], "message": "Required" }
    ],
    "name": "ZodError"
  }
}

// 500 Internal Server Error
{
  "success": false,
  "error": "Internal server error. Please try again later.",
  "code": 500
}

// 502 Property Finder upstream unavailable
{
  "success": false,
  "error": "Service temporarily unavailable. Please try again later.",
  "code": 502
}

Quick Reference