Number of Data Files / Resources 1
Updated: 25 May 2023
The dataset represents the service entity wise transaction details
Request Permission

I acknowledge that I have read and agree to the terms and conditions

Send Request
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.
Send Feedback
Updated: 25 May 2023 File Size : 28.95 MB
Field Value
Data Provenance 1. All service entity transactions are considered for the data se
Dataset Source Relational Database
Format CSV
Created 01 Oct 2020
Last updated 25 May 2023
Frequency of Update on Source RealTime
Frequency of Update to SDP
Expected Volume/Ingestion Cycle(Daily if Real-time)
800 records monthly
Language English~English~English~English~Mix~English~English~Mix~Mix~English
State active
License notspecified
Name Description Primary Key Size Datatype Foreign Key Range of Values Language Classification
project_no Project Number Yes 22 numeric Yes English Open
parcel_id represents the parcel id in which the building resides No 15 nvarchar No English Open
application_no Permit Applicatiojn Number Yes 100 nvarchar Yes English Open
service_entity_id Service entity id Yes 22 numeric No English Open
service_entity Service entity Name No 250 nvarchar No Mix Open
application_submission_date Application Submission Date No 10 date No yyyy-mm-dd English Open
app_completion_date Application completion date No 10 date No yyyy-mm-dd English Open
final_status Service entity final decision No 1000 nvarchar No Mix Open
initial_status Service entity initial decision No 1000 nvarchar No Mix Open
final_status_decision_date Service entity final decision date No 10 date No yyyy-mm-dd English Open

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
  • 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: 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" ""
  • Query Samples: AND zone_id=2 OR zone_id=2
  • Record Limit Sample:
  • Record Offset Sample:
  • Record Order By Sample:
  • Attribute Limiting Sample: OR zone_id=2 &column=zone_id,line_name,location_id