Number of Data Files / Resources 17
Updated: 10 Oct 2021
The ticket details for all ticketed events
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: 10 Oct 2021 File Size : 0.01 MB
Updated: 20 Sep 2021 File Size : 0.01 MB
Updated: 03 Aug 2021 File Size : 0.00 MB
Updated: 27 Apr 2021 File Size : 0.01 MB
Updated: 13 Jan 2021 File Size : 0.00 MB
Updated: 04 Oct 2020 File Size : 0.00 MB
Field Value
Data Provenance Attendee can get the ticket from sales points Phisical/online one attendee can get more than one ticket once event is available for public the customer can buy the ticket for that event
Dataset Source e-ticketing
Format CSV
Created 16 Feb 2018
Last updated 10 Oct 2021
Frequency of Update on Source Upon transaction
Frequency of Update to SDP
Expected Volume/Ingestion Cycle(Daily if Real-time)
Approximatly 1049916 Records for 3 months
Language English~English~English~English~English~English~English~English~English~English~English
State active
Rights N/A
License notspecified
Name Description Primary Key Size Datatype Foreign Key Range of Values Language Classification
event_config Event Configuration Type (Seated/General Admission) Yes String English Open
event_description EventDescription Yes String English Open
show Show name Yes String English Open
venue Venue Yes String English Open
show_date Date of the individual show, an event may include more than one show Yes String English Open
show_time show time within the day Yes String English Open
show_type Type of the show e.g. car racing, drama, dj Yes String English Open
ticket_category class of the ticket Yes String English Open
seller_code Code of the Establishment selling the Yes String English Open
ticket_price Price of the ticket Yes String English Open
permit_number PermitNumber Yes String 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