Heureka

Heureka is one of the largest price comparison and shopping advisor platforms in Europe, providing comprehensive product information, price tracking, and affiliate marketing services to help consumers make informed purchasing decisions and businesses optimize their online presence.

Power end-to-end data operations for your Heureka API with Nexla. Our bi-directional Heureka connector is purpose-built for Heureka, making it simple to ingest data, sync it across systems, and deliver it anywhere — all with no coding required. Nexla turns API-sourced data into ready-to-use, reusable data products and makes it easy to send data to Heureka or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Heureka workflows fast, secure, and fully governed.

Features

Type: API

SourceDestination

• Seamless API Integration: Connect to any endpoint as source or destination without coding, with automatic data product creation
• Visual Composition & Chaining: Build complex integrations using visual templates, chain API calls, and compose workflows with data validation and filtering
• API Proxy: Expose curated slices of your data securely with a secure and customizable API proxy that validates and transforms data on the fly
• Request optimization with intelligent batching, retry, and caching to minimize API calls and costs

Prerequisites

Before creating a Heureka credential, you need to obtain a Public Key and Private Key from your Heureka account. The Public Key and Private Key are required for HMAC authentication with the Heureka API.

To obtain your Public Key and Private Key, you need to have a Heureka producer account. Once you have access to your account, you can view and manage your API keys in your account settings. The Public Key and Private Key are used to generate HMAC signatures for API requests, which are required for authentication with the Heureka API. For detailed information about HMAC authentication setup, refer to the Heureka API documentation.

Authenticate

Credentials required

Field	Required	Secret	Description
Public Key	Yes	Yes	Public Key
Private Key	Yes	Yes	Private Key
Base URL	No	No	Base URL for exporting the data Allowed values: heureka.cz (heureka.cz (Czech)); heureka.sk (heureka.sk (Slovak))

Create a credential in Nexla

1. After selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.

New Credential Overlay – Heureka

2. Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.

3. Enter your Heureka Public Key in the Public Key field. This is the Public Key you obtained from your Heureka account settings. The Public Key is used along with the Private Key to generate HMAC signatures for API requests. The default value is kasnvjaoiag if not specified.

   Your Heureka Public Key can be found in your Heureka producer account settings. The Public Key is used along with the Private Key to generate HMAC signatures for API requests. The Public Key is included in the request signature calculation. For detailed information about finding your Public Key, see the Heureka API documentation.

4. Enter your Heureka Private Key in the Private Key field. This is the Private Key you obtained from your Heureka account settings. The Private Key is used along with the Public Key to generate HMAC signatures for API requests. The default value is gahpiev6ei if not specified.

   Keep your Private Key secure and do not share it publicly. The Private Key provides access to your Heureka account data and should be treated as sensitive information. Your Heureka Private Key can be found in your Heureka producer account settings. The Private Key is used along with the Public Key to generate HMAC signatures for API requests. The Private Key is used as the secret key in the HMAC signature calculation. For detailed information about finding your Private Key, see the Heureka API documentation.

5. Select or enter the base URL for exporting data from the Base URL field. Available options include https://export-api.heureka.cz/cz/producer for heureka.cz (Czech) and https://export-api.heureka.sk/sk/producer for heureka.sk (Slovak). You can also add custom base URLs if needed. The base URL determines which Heureka platform and region your API requests will be sent to.

   The Base URL determines which Heureka platform and region your API requests will be sent to. Available options include heureka.cz (Czech) and heureka.sk (Slovak). You can also add custom base URLs if needed. The base URL is used to construct the full endpoint URLs for API requests. For detailed information about available base URLs and regions, see the Heureka API documentation.

6. Click the Save button at the bottom of the overlay. The newly added credential will now appear in a tile on the Authenticate screen during data source/destination creation.

Use as a data source

To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Select the Heureka connector tile, then select the credential that will be used to connect to the Heureka account, and click Next; or, create a new Heureka credential for use in this flow.

Endpoint templates

Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common Heureka endpoints. Select the endpoint from which this source will fetch data from the Endpoint pulldown menu. Available endpoint templates are listed in the expandable boxes below.

Get all Products by Producer

Get all Products by Producer

• This endpoint automatically retrieves all products associated with your Heureka producer account. No additional configuration is required beyond selecting this endpoint template.
• The endpoint uses GET requests to the Base URL you configured in your credential (e.g., https://export-api.heureka.cz/cz/producer for heureka.cz or https://export-api.heureka.sk/sk/producer for heureka.sk). The endpoint URL is automatically constructed based on your Heureka API base URL from the credential configuration.
• The endpoint uses HMAC authentication, which requires a Public Key and Private Key to generate cryptographic signatures for API requests. The HMAC signature is automatically generated and included in the request using your credential configuration.
• The endpoint does not use pagination (iteration.type: static.url) and returns a single response. The response data path is /products, which extracts the products data from the XML response.
• The endpoint returns data in XML format, which Nexla automatically parses and converts into structured data that can be used in your data flows.

This endpoint retrieves all products associated with your Heureka producer account. The endpoint uses HMAC authentication, which requires a Public Key and Private Key to generate cryptographic signatures for API requests. The HMAC signature is automatically generated and included in the request using your credential configuration. The endpoint returns data in XML format, which Nexla automatically parses and converts into structured data. The Base URL you configured in your credential determines which Heureka platform (heureka.cz or heureka.sk) and region your API requests will be sent to. For detailed information about the API response format and available fields, see the Heureka API documentation.

Once the selected endpoint template has been configured, click the Test button to the right of the endpoint selection menu to retrieve a sample of the data that will be fetched. Sample data will be displayed in the Endpoint Test Result panel on the right, allowing you to verify that the source is configured correctly before saving.

Manual configuration

Heureka data sources can also be manually configured to ingest data from any valid Heureka API endpoint, including endpoints not covered by the pre-built templates or when you need custom API configurations. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the content format, API method, endpoint URL, date/time and lookup macros, path to data, metadata, and request headers.

The Heureka API typically returns data in XML format. Heureka API endpoints typically follow the pattern https://export-api.heureka.{region}/{locale}/producer/{endpoint_path}, where {region} is the region (cz or sk) and {locale} is the locale (cz or sk). The endpoint requires HMAC authentication using your Public Key and Private Key, which is handled automatically by your credential configuration.

Once all of the relevant settings have been configured, click the Create button in the upper right corner of the screen to save and create the new Heureka data source. Nexla will now begin ingesting data from the configured endpoint and will organize any data that it finds into one or more Nexsets.