Skip to main content


The Qlik OData Connector accesses website data and streams it into SaaS editions of Qlik Sense. OData (Open Data Protocol) is a standard that defines the best practice for building and consuming RESTful APIs.

Note: This OData connector is only available in SaaS editions of Qlik Sense. For the client managed version, see Qlik Web Connectors: OData.

The Qlik OData Connector can access a large number of data sets, including:

  • Those listed in the OData ecosystem.

  • Microsoft Dynamics CRM: You should be able to use [Your Organization RootURL]/XRMServices/2011/OrganizationData.svc as the service end point. This is for locally hosted Dynamics installations only.

Supported offerings

  • Qlik Sense Business
  • Qlik Sense Enterprise SaaS

Ways to access your data

You can access the following data sets using the Qlik OData Connector:

  • Websites that expose their data using the OData protocol, see: Ecosystem: Producers.

  • Data sets that are hosted on SharePoint server 2010 or 2013.
  • Microsoft Dynamics CRM data that is locally hosted.

You need to obtain the OData service URL for the dataset that you want to connect to. The OData connector supports basic authentication and auth header authentication.

Loading data from tables

After authenticating the connector, a number of tables are available:

Tables that can be loaded
Table Description
ListResources Returns a list of the available tables and resources. You will need to enter parameters to load the data.
GetData This is used to get resource or table data. Column names ending in _Feed or _Entry can be used as new inputs for Resource parameters. You will need to enter parameters to load the data.


If you are connecting to your own OData server and are getting out-of-memory exceptions, particularly for requests that return very large data sets, you should make sure that paging is enabled for your OData server.


The OData connector has the following limitations:

  • OData only allows HTTPS URLs.

  • JSON is not supported.

  • The Test connection option only checks for a 200/OK. Because of this, it is possible to authenticate successfully to a service that only provides JSON , then not be able to actually pull any JSON data.

Reference - OData documentation

You can refer to the OData documentation to learn more about the requirements and restrictions imposed by the OData API.

OData API Introduction