Warning: BETA. This connector is a beta version.


The Qlik Strava connector uses the Strava API v3 to fetch your athletic activity stats from Strava.

Note: The built-in web connectors are only available on Qlik Sense Cloud with a Cloud Business subscription.

Ways to access your data

To access your Strava data, you need to authenticate the connector with your Strava account credentials. After you create a connection and select Strava as your data source, you are redirected to a Strava login page. Log in with your credentials to retrieve an authentication code, and enter it into the connector.

Creating a connection and selecting data

Loading data from tables

After you authenticate the connector with your account credentials, you can use the following tables to select and load data: 

Table Description
Stats Use this to see the stats of your most recent, year-to-date, and all-time activities.
Activities Use this to see the activities for the authenticated athlete.
Athlete Use this to see a summary for the authenticated athlete.

To select and load data from a table, enter the required table parameters and click Preview data. Required parameters are marked with an asterisk (*). The table fields are displayed under the Data preview tab. You can select fields individually by selecting the box beside each field name. Select Insert script after you have made your selection.

Creating a connection and selecting data

Working with the Strava API quota limits

The Qlik Web Connectors use the Strava API v3 to extract data from Strava and load it into your Qlik Sense app. While reloading your Strava-based app, you might receive an error message that the connector has reached the Strava API v3 rate limit and that all subsequent API calls will fail until the connector falls back under the throttling limit. If you receive this error message, then you have exceeded one of the API rate limits.


You receive an error message that you have reached the API rate limit

Possible cause

You have exceeded the API limits that are imposed by the Strava API v3.

Proposed action

To reduce the impact of reaching API rate limits, develop your app with the following in mind:

  • Extract only the data you need.
  • Reload one Strava-based application at a time.
  • Ensure that loops in your script that make API calls do not result in infinite loops.

Did this information help you?

Thanks for letting us know. Is there anything you'd like to tell us about this topic?

Can you tell us why it did not help you and how we can improve it?