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
CSV
CSV
CSV
CSV
CSV
| Field | Value | |||||||
|---|---|---|---|---|---|---|---|---|
| Data Provenance | Event Organizers should apply for Event permit from DTCM Organizer and Venue name should be entered exactly as in trade license Event can have multiple venues or none Events can be registered in the system 5 days - 6 months in advance. Event Start Date should be at least 5 days from the date of submission the application for permit that not require technical approval. Additionally, Event Start Date should be at least 30 days from the date of submission the application for the permit that require technical approval All events in Dubai as per DTCM definition of event refer to 'Executive Resolution - Marketing & Distribution of Tickets within the Emirate of Dubai' | |||||||
| Dataset Source | e-permits | |||||||
| Format | CSV | |||||||
| Created | 16 Feb 2018 | |||||||
| Last updated | 04 Oct 2023 | |||||||
| Frequency of Update on Source | Upon transaction | |||||||
|
Frequency of Update to SDP
|
Quarterly
|
|||||||
|
Expected Volume/Ingestion Cycle(Daily if Real-time)
|
Approximatly 581 Records for 3 months
|
|||||||
| Language | English~English~English~English~English~English~English~~~~~English~English~English~English~English | |||||||
| State | active | |||||||
| Rights | N/A | |||||||
| License | notspecified | |||||||
| Show more | ||||||||
| Name | Description | Size | Datatype | Foreign Key | Range of Values | Language | Classification | |
|---|---|---|---|---|---|---|---|---|
| permit_number | Event permit number generated by DTCM e-permits system | 40 | String | English | Open | |||
| organizer_name | Name of Establishment organizing the event | 255 | String | English | Open | |||
| organizer_id | Establishment organizing the event - ID generated by DTCM e-permits system | 40 | String | English | Open | |||
| event_name | Name of the event | 4000 | String | English | Open | |||
| ticketed | Flag indecates that event is ticketed or not | 3 | String | English | Open | |||
| event_type | Category of the event, entertainment, business …. | 1000 | String | English | Open | |||
| event_subtype | Subcategory for each event, e.g. Event Type Entertainment Subtype - Fashion Show | 1000 | String | English | Open | |||
| venue_name | Name of the event venue | 1000 | String | Open | ||||
| venue_id | Generated Venue ID by DTCM system | 40 | String | Open | ||||
| venue_address | GPS coordinates of the event venue where available | 1000 | String | Open | ||||
| sub_venue_name | Name of the Hall/Area were the show will be held | 40 | String | Open | ||||
| event_start_date | Starting date of the event | Date (DD/MM/YYYY) | English | Open | ||||
| event_end_date | Ending date of the event | Date (DD/MM/YYYY) | English | Open | ||||
| event_start_time | Event starting time | Time (HH:Mi:SS) | English | Open | ||||
| event_end_time | Event ending time | Time (HH:Mi:SS) | English | Open | ||||
| sub_venue_capacity | Capacity of the event hall | Integer | English | 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/cfd543aa-3631-47a8-a660-541ce96a5011/resource/25aaceb7-5df4-4f11-9271-ae10375f70d2/download/epermit_2017-08-30_04-03-56.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