Your request has been successfully submitted
You will receive a confirmation within 14days time period. If you are
having any query feel free to contact us.
having any query feel free to contact us.
Done
Send Feedback
CSV
| Field | Value | |||||||
|---|---|---|---|---|---|---|---|---|
| Data Provenance | All sales, mortgage, inheritance, merge, separation and sub-separation transactions are recorded by Dubai Land Dept. | |||||||
| Dataset Source | TABU System | |||||||
| Format | CSV | |||||||
| Created | 06 Apr 2022 | |||||||
| Last updated | 24 Jan 2025 | |||||||
| Frequency of Update on Source | Daily | |||||||
|
Frequency of Update to SDP
|
Daily
|
|||||||
|
Expected Volume/Ingestion Cycle(Daily if Real-time)
|
598907
|
|||||||
| Language | English~Arabic~English~English~Arabic~English~English~Arabic~English~English~English~English~Arabic~English~English~English~English~Arabic~English~English~Arabic~Arabic~English~Arabic~English~Arabic~English~Arabic~English~English~English~English~English~English~English~English~English~English~Arabic~English~Arabic~English~Arabic~English~English~Arabic | |||||||
| State | active | |||||||
| Rights | No,Personal Information (DNRD), | |||||||
| License | notspecified | |||||||
| Show more | ||||||||
| Name | Description | Primary Key | Size | Datatype | Foreign Key | Range of Values | Language | Classification |
|---|---|---|---|---|---|---|---|---|
| property_sub_type_en | sub type of the property (ex. For units : apartment , shop , office ..etc) | No | 100 | nvarchar | English | Open | ||
| property_usage_ar | property use based zoning authority's regulations (Residential , Commercial , Industrial .. Etc) in Arabic | No | 100 | nvarchar | Arabic | Open | ||
| property_usage_en | property use based zoning authority's regulations (Residential , Commercial , Industrial .. Etc) | No | 100 | nvarchar | English | Open | ||
| reg_type_id | Type of registration (off-plan or existing properties) | No | 1 | numeric | English | Open | ||
| reg_type_ar | Type of registration (off-plan or existing properties) in Arabic | No | 100 | nvarchar | Arabic | Open | ||
| reg_type_en | Type of registration (off-plan or existing properties) | No | 100 | nvarchar | English | Open | ||
| area_id | Area (community) ID | No | 10 | numeric | English | Open | ||
| area_name_ar | community name in Arabic as per Dubai Municipality | No | 200 | nvarchar | Arabic | Open | ||
| area_name_en | community name in English as per Dubai Municipality | No | 200 | nvarchar | English | Open | ||
| transaction_id | A Unique ID of the transaction | Yes | 100 | nvarchar | English | Open | ||
| procedure_id | number generated through the system | No | 3 | numeric | English | Open | ||
| trans_group_id | The unique ID of transaction group | No | 3 | numeric | English | Open | ||
| trans_group_ar | high level group type of the transaction (Sales , Mortgages , Gifts) | No | 200 | nvarchar | Arabic | Open | ||
| trans_group_en | high level group type of the transaction (Sales , Mortgages , Gifts) in Arabic | No | 200 | nvarchar | English | Open | ||
| procedure_name_en | Sub type of the transaction (pre-registration sale , delayed sale , update mortgage , release mortgage ..etc) | No | 200 | nvarchar | English | Open | ||
| instance_date | Transaction registration data | No | 10 | date | DD-MM-YYYY | English | Open | |
| project_number | Developer's project number | No | 30 | numeric | English | Open | ||
| project_name_ar | Developer's project Arabic name | No | 200 | nvarchar | Arabic | Open | ||
| project_name_en | Developer's project English name | No | 200 | nvarchar | English | Open | ||
| master_project_en | master developer name in Arabic | No | 200 | nvarchar | English | Open | ||
| master_project_ar | master developer name in English | No | 200 | nvarchar | Arabic | Open | ||
| nearest_landmark_ar | the nearest landmark to the property of the transaction in Arabic | No | 200 | nvarchar | Arabic | Open | ||
| nearest_landmark_en | the nearest landmark to the property of the transaction in English | No | 200 | nvarchar | English | Open | ||
| nearest_metro_ar | the nearest metro station to the property of the transaction in Arabic | No | 200 | nvarchar | Arabic | Open | ||
| nearest_metro_en | the nearest metro station to the property of the transaction In English | No | 201 | nvarchar | English | Open | ||
| nearest_mall_ar | the nearest mall to the property of the transaction in Arabic | No | 202 | nvarchar | Arabic | Open | ||
| nearest_mall_en | the nearest mall to the property of the transaction in English | No | 203 | nvarchar | English | Open | ||
| rooms_ar | number of rooms in Arabic | No | 200 | nvarchar | Arabic | Open | ||
| rooms_en | number of room in English | No | 200 | nvarchar | English | Open | ||
| has_parking | does the unit has a parking ? (0=No, 1=Yes) | No | 1 | numeric | English | Open | ||
| procedure_area | The area (size) in suare meter on which the transaction was carried out | No | 18 | numeric | English | Open | ||
| actual_worth | property price in the transaction | No | 20 | numeric | English | Open | ||
| meter_sale_price | meter price in the transaction | No | 18 | numeric | English | Open | ||
| rent_value | the mortgage value in lease to own procedures | No | 20 | numeric | English | Open | ||
| meter_rent_price | the mortgage price per meter in lease to own procedures | No | 20 | numeric | English | Open | ||
| no_of_parties_role_1 | number of transaction's parties with first role (seller , mortgagor .. Etc ) | No | 3 | numeric | English | Open | ||
| no_of_parties_role_2 | number of transaction's parties of second role (buyer , mortgagee .. Etc ) | No | 3 | numeric | English | Open | ||
| no_of_parties_role_3 | number of transaction's parties of third role (lessee , usufrutor .. Etc ) | No | 3 | numeric | English | Open | ||
| building_name_ar | Building name in Arabic a given by the developer (not nessesarly to similar to common name) | No | 200 | nvarchar | Arabic | Open | ||
| building_name_en | Building name in English given by the developer (not nessesarly to similar to common name) | No | 200 | nvarchar | English | Open | ||
| procedure_name_ar | Sub type of the transaction (pre-registration sale , delayed sale , update mortgage , release mortgage ..etc) in Arabic | No | 200 | nvarchar | Arabic | Open | ||
| property_type_id | number generated through the system | No | 4 | numeric | English | Open | ||
| property_type_ar | main type of the property (land , Building , villa or unit) in Arabic | No | 50 | nvarchar | Arabic | Open | ||
| property_type_en | main type of the property (land , Building , villa or unit) | No | 50 | nvarchar | English | Open | ||
| property_sub_type_id | PROPERTY_SUB_TYPE_ID | No | 10 | numeric | English | Open | ||
| property_sub_type_ar | sub type of the property (ex. For units : apartment , shop , office ..etc) in Arabic | No | 100 | nvarchar | Arabic | Open | ||
| Show more Show less | ||||||||
Dubai Pulse Data API
Access resource data via a web API with powerful query support.
The Data API can be accessed via the following actions of the CKAN action API.
-
Query
https://www.dubaipulse.gov.ae/dataset/3b25a6f5-9077-49d7-8a1e-bc6d5dea88fd/resource/a37511b0-ea36-485d-bccd-2d6cb24507e7/download/transactions.csv
-
End Users will receive "API Key" and "API Secret" in two separate emails on the first time Grant of a Dataset, first Purchase of a Commercial Dataset, or Purchase of an API Package. This API Key and API Secret combination should be used to generate API token and the token will need to be included in the http headers of every API call made.
Authentication Service to generate API token: https://api.dubaipulse.gov.ae/oauth/client_credential/accesstoken?grant_type=client_credentials with body 'client_id={API Key}&client_secret={API Secret}
Read the value of "access_token" from the response of the above service and use it in the header of every API call. The obtained API token is valid for certain duration (for example 30 minutes) after which a fresh token needs to be obtained.
Header Name : Authorization Value : Bearer {access_token}
-
Query Parameters
API calls can be made for full dataset result (subject to maximum results limit) or to a subset of results. Different filters can be applied on the results. Developers can use the attributes to apply a combination of filters with and/or conditions.
-
Limiting the Response Size
Developers can limit the number of records returned by an API call passing the "Limit" parameter in the call. The value of the "Limit" must be less than the allowed maximum limit.
-
Limiting the Attributes
Developers can limit the API response to specific set of attributes by passing the attribute names in the API call. The example below explains how the attributes can be specified in the API call. This feature can be used in conjunction with query parameters.
-
Curl Command Sample:
curl -X GET --header "Authorization: qMtn6xQapeouAlirfHXD7DWJFabV" "https://api.dubaipulse.gov.ae/shared/rta/rta_tram_stations-open-api"
-
Query Samples:
https://api.dubaipulse.gov.ae/shared/rta/rta_tram_stations-open-api?filter=location_id=223 AND zone_id=2 https://api.dubaipulse.gov.ae/shared/rta/rta_tram_stations-open-api?filter=location_id=223 OR zone_id=2
-
Record Limit Sample:
https://api.dubaipulse.gov.ae/shared/rta/rta_tram_stations-open-api?limit=10
-
Record Offset Sample:
https://api.dubaipulse.gov.ae/shared/rta/rta_tram_stations-open-api?order_by=primary_key_attribute&offset=10
-
Record Order By Sample:
https://api.dubaipulse.gov.ae/shared/rta/rta_tram_stations-open-api?order_by=location_id
-
Attribute Limiting Sample:
https://api.dubaipulse.gov.ae/shared/rta/rta_tram_stations-open-api?filter=location_id=223 OR zone_id=2 &column=zone_id,line_name,location_id