Skip to main content Skip to complementary content

AYLIEN News V2

The Qlik AYLIEN News V2 connector uses the AYLIEN News API to gather data from news articles and load this information into your Qlik Sense app.

Information noteThis AYLIEN News V2 connector is only available in Qlik Sense SaaS. For the client managed version, see Qlik Web Connectors: AYLIEN News V2.

Supported offerings

  • Qlik Sense Business
  • Qlik Sense Enterprise SaaS

Ways to access your data

To access your AYLIEN News data, you need to authenticate the connector with your AYLIEN News account credentials. After you create a new connection and select AYLIEN News as your data source, you need to enter the app id and app key credentials from your AYLIEN News account.

Creating a data source connection

Loading data from tables

After you authenticate the connector with the app id and app key, you can use the following tables to select and load data: 

Tables that can be loaded
Table Available in Description
Search Data manager and Data load editor Allows you to search for news stories.
Story Data load editor Retrieves a specific story by ID.
RelatedSearch Data load editor Retrieves stories related to a specific story ID.
Coverage Data load editor Retrieves coverages for a story.
TimeSeries Data load editor Retrieves time series.
Trends Data load editor Used for finding trends.

To select and load data from a table, enter the required table parameters and click Preview data. Required parameters are marked with an asterisk (*) in the dialog. 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

Migration of the new AYLIEN News API

This version of the connector works with the latest AYLIEN News API. App IDs may be specific to only one version of the API:

If you signed up as an AYLIEN News user before October 29th 2019 you may only be able to use v1 of this connector, which is using the legacy API.

If you signed up after October 29th 2019 you may only be able to use this version of the connector, which is using the latest API. AYLIEN are migrating legacy app IDs so it is advisable to check whether your app ID has been migrated. When the legacy API is retired all users will have to use AYLIEN News V2 connector.

Working with the AYLIEN News API quota limits

The Qlik Web Connectors use the AYLIEN News API to extract data from AYLIEN and load it into your Qlik Sense app. While reloading your AYLIEN-based app, you might receive an error message that the connector has reached the AYLIEN News API 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.

Reference - AYLIEN News documentation

You can refer to the new AYLIEN News API documentation to learn more about the requirements and restrictions imposed by the AYLIEN News API V2.0.

Limitations

Note that the source_description and source_links_in_count columns are not currently supported in V2 of this connector so you may need to update scripts if you were previously using these columns with V1.

Troubleshooting

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 your AYLIEN News API app key.

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 AYLIEN-based application at a time.
  • Ensure that loops in your script that make API calls do not result in infinite loops.

You receive the error message 'application with id=XYZ was not found' during authentication

Possible cause

You are using the wrong version of this connector, or your app ID has not yet been migrated by AYLIEN.

Proposed action

Check whether your app ID has been migrated by AYLIEN.

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – let us know how we can improve!