Tune Network is an affiliate marketing platform that provides comprehensive tracking, reporting, and management tools for advertisers and publishers to optimize their affiliate marketing campaigns and partnerships.
Power end-to-end data operations for your Tune Network API with Nexla. Our bi-directional Tune Network connector is purpose-built for Tune Network, 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 Tune Network or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Tune Network 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
Before creating a Tune Network credential, you need to obtain your Network ID and API Key (NetworkToken) from your Tune Network account. Tune Network uses API key authentication for all API requests, with the token sent as a URL parameter (NetworkToken).
To obtain your Tune Network credentials, follow these steps:
Sign in to your Tune Network account using your administrator credentials.
Navigate to Settings or API Settings in your Tune Network account, typically accessible from the account menu or settings icon.
In the Settings menu, navigate to API or Developer Settings to access API configuration options.
Look for the Network ID and API Key (NetworkToken) section in your Tune Network settings.
Your Network ID is typically displayed in your account settings or can be found in your Tune Network dashboard. The Network ID is used to construct the API endpoint URL (e.g., https://{network_id}.api.hasoffers.com).
If you don't have an API key yet, click Create API Key or Generate NetworkToken to create a new API key.
Configure your API key settings:
Enter a name for the API key (e.g., "Nexla Integration")
Review and select the permissions or scopes for the API key (if applicable)
Set an expiration date if required (optional)
Click Create or Generate to create the API key.
Copy the API Key (NetworkToken) immediately after it's generated, as it may not be accessible again after you navigate away from the page.
Store both credentials securely, as you will need them to configure your Nexla credential. The API key is sensitive information and should be kept confidential.
The Network ID is used to construct the API endpoint URL (e.g., https://{network_id}.api.hasoffers.com), and the API key (NetworkToken) is sent as a URL parameter (NetworkToken) for all API requests to the Tune Network API. The token authenticates your requests and grants access to Tune Network resources based on your account permissions. If your API key is compromised, you should immediately revoke it in your Tune Network account settings and generate a new one. For detailed information about obtaining API credentials, API authentication, and available endpoints, refer to the Tune Network API documentation.
After selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.
New Credential Overlay – Tune Network
Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.
Tune Network uses API key authentication for all API requests. The Network ID is used to construct the API endpoint URL, and the API key (NetworkToken) is sent as a URL parameter.
Enter your Network ID in the Network ID field. This is your Tune Network ID that is used to construct the API endpoint URL (e.g., https://{network_id}.api.hasoffers.com). The Network ID can be found in your Tune Network account settings or dashboard.
Enter your API Key in the API Key field. This is the NetworkToken you obtained from your Tune Network account settings (Settings > API or Developer Settings). The API key is sent as a URL parameter (NetworkToken) for all API requests to the Tune Network API. The API key is sensitive information and must be kept confidential.
Your Tune Network credentials (Network ID, API Key) can be found in your Tune Network account settings under Settings > API or Developer Settings. The Network ID is used to construct the API endpoint URL, and the API key (NetworkToken) is sent as a URL parameter (NetworkToken) for all API requests to the Tune Network API.
If your API key is compromised, you should immediately revoke it in your Tune Network account settings and generate a new one. The API key provides access to your Tune Network account data and should be treated as sensitive information. Keep your API key secure and do not share it publicly.
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.
To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Select the Tune Network connector tile, then select the credential that will be used to connect to the Tune Network instance, and click Next; or, create a new Tune Network credential for use in this flow.
Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common Tune Network endpoints. Each template is designed specifically for the corresponding Tune Network endpoint, making data source setup easy and efficient. 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 Entities from Tune
This endpoint template retrieves all ad campaign objects from your Tune Network account. Use this template when you need to access ad campaign information, campaign status, or campaign metadata for analysis, reporting, or integration purposes.
Optionally enter the Status of Ad campaign in the Status of Ad campaign field. This should be the status filter for the ad campaigns you want to retrieve (e.g., active, paused, deleted). The Status determines which ad campaigns will be retrieved. You can select from the available options: Active, Paused, or Deleted. If left empty, all ad campaigns will be retrieved. The endpoint uses incrementing page number pagination to handle large datasets efficiently, returning up to 100 records per page by default.
This endpoint returns all ad campaign objects from your Tune Network account, including campaign IDs, names, status, and other campaign metadata. The endpoint uses incrementing page number pagination with page and limit parameters to handle large datasets efficiently. Nexla will automatically follow the pagination to fetch subsequent pages of data.
For detailed information about ad campaigns, API response structures, pagination, and available campaign data, see the Tune Network API documentation.
Get Ad Campaign Creatives by filters
This endpoint template retrieves ad campaign creatives filtered by status and ad campaign ID from your Tune Network account. Use this template when you need to access creative information, creative assets, or creative metadata for specific ad campaigns for analysis, reporting, or integration purposes.
Optionally enter the Status in the Status field. This should be the status filter for the creatives you want to retrieve (e.g., active, paused, deleted). The Status determines which creatives will be retrieved. You can select from the available options: Active, Paused, or Deleted. If left empty, all creatives matching the other filters will be retrieved.
Optionally enter the Ad Campaign ID in the Ad Campaign ID field. This should be the unique identifier of the ad campaign whose creatives you want to retrieve. The Ad Campaign ID determines which ad campaign's creatives will be retrieved. You can find the Ad Campaign ID by using the "Get Entities from Tune" endpoint. The default value is 1. The endpoint uses incrementing page number pagination to handle large datasets efficiently.
This endpoint returns ad campaign creatives filtered by status and ad campaign ID from your Tune Network account, including creative IDs, names, status, and other creative metadata. The endpoint uses incrementing page number pagination with page and limit parameters to handle large datasets efficiently. Nexla will automatically follow the pagination to fetch subsequent pages of data.
The Ad Campaign ID can be found by using the "Get Entities from Tune" endpoint. For detailed information about creatives, API response structures, pagination, and available creative data, see the Tune Network API documentation.
Get Advertisers
This endpoint template retrieves all advertisers from your Tune Network account. Use this template when you need to access advertiser information, advertiser status, or advertiser metadata for analysis, reporting, or integration purposes.
Optionally enter the Status in the Status field. This should be the status filter for the advertisers you want to retrieve (e.g., pending, active, blocked, deleted, rejected). The Status determines which advertisers will be retrieved. You can select from the available options: Pending, Active, Blocked, Deleted, or Rejected. If left empty, all advertisers will be retrieved. The endpoint uses incrementing page number pagination to handle large datasets efficiently, returning up to 100 records per page by default.
This endpoint returns all advertisers from your Tune Network account, including advertiser IDs, names, status, and other advertiser metadata. The endpoint uses incrementing page number pagination with page and limit parameters to handle large datasets efficiently. Nexla will automatically follow the pagination to fetch subsequent pages of data.
For detailed information about advertisers, API response structures, pagination, and available advertiser data, see the Tune Network API documentation.
Get advertiser invoices
This endpoint template retrieves advertiser invoices filtered by payment status, sent status, and invoice status from your Tune Network account. Use this template when you need to access invoice information, billing data, or invoice metadata for analysis, reporting, or integration purposes.
Optionally enter the Is Paid in the Is Paid field. This should be the payment status filter for the invoices you want to retrieve (True for paid invoices, False for unpaid invoices). The Is Paid determines which invoices will be retrieved. You can select from the available options: Yes (True) or No (False). If left empty, all invoices matching the other filters will be retrieved.
Optionally enter the Is Sent in the Is Sent field. This should be the sent status filter for the invoices you want to retrieve (True for sent invoices, False for unsent invoices). The Is Sent determines which invoices will be retrieved. You can select from the available options: Yes (True) or No (False). If left empty, all invoices matching the other filters will be retrieved.
Optionally enter the Status in the Status field. This should be the invoice status filter for the invoices you want to retrieve (e.g., active, incomplete, deleted). The Status determines which invoices will be retrieved. You can select from the available options: Active, Incomplete, or Deleted. If left empty, all invoices matching the other filters will be retrieved. The endpoint uses incrementing page number pagination to handle large datasets efficiently, returning up to 100 records per page by default.
This endpoint returns advertiser invoices filtered by payment status, sent status, and invoice status from your Tune Network account, including invoice IDs, amounts, payment status, and other invoice metadata. The endpoint uses incrementing page number pagination with page and limit parameters to handle large datasets efficiently. Nexla will automatically follow the pagination to fetch subsequent pages of data.
For detailed information about advertiser invoices, API response structures, pagination, and available invoice data, see the Tune Network API documentation.
Get Advertiser User
This endpoint template retrieves advertiser users filtered by status from your Tune Network account. Use this template when you need to access advertiser user information, user status, or user metadata for analysis, reporting, or integration purposes.
Optionally enter the Status in the Status field. This should be the status filter for the advertiser users you want to retrieve (e.g., active, blocked, deleted). The Status determines which advertiser users will be retrieved. You can select from the available options: Active, Blocked, or Deleted. If left empty, all advertiser users will be retrieved. The endpoint uses incrementing page number pagination to handle large datasets efficiently, returning up to 100 records per page by default.
This endpoint returns advertiser users filtered by status from your Tune Network account, including user IDs, names, status, and other user metadata. The endpoint uses incrementing page number pagination with page and limit parameters to handle large datasets efficiently. Nexla will automatically follow the pagination to fetch subsequent pages of data.
For detailed information about advertiser users, API response structures, pagination, and available user data, see the Tune Network API documentation.
Get Affiliate
This endpoint template retrieves affiliates filtered by status from your Tune Network account. Use this template when you need to access affiliate information, affiliate status, or affiliate metadata for analysis, reporting, or integration purposes.
Optionally enter the Status in the Status field. This should be the status filter for the affiliates you want to retrieve (e.g., pending, active, blocked, deleted, rejected). The Status determines which affiliates will be retrieved. You can select from the available options: Pending, Active, Blocked, Deleted, or Rejected. If left empty, all affiliates will be retrieved. The endpoint uses incrementing page number pagination to handle large datasets efficiently, returning up to 100 records per page by default.
This endpoint returns affiliates filtered by status from your Tune Network account, including affiliate IDs, names, status, and other affiliate metadata. The endpoint uses incrementing page number pagination with page and limit parameters to handle large datasets efficiently. Nexla will automatically follow the pagination to fetch subsequent pages of data.
For detailed information about affiliates, API response structures, pagination, and available affiliate data, see the Tune Network API documentation.
Get Offers
This endpoint template retrieves offers filtered by status from your Tune Network account. Use this template when you need to access offer information, offer status, or offer metadata for analysis, reporting, or integration purposes.
Optionally enter the Status in the Status field. This should be the status filter for the offers you want to retrieve (e.g., pending, active, paused, deleted, expired). The Status determines which offers will be retrieved. You can select from the available options: Pending, Active, Paused, Deleted, or Expired. If left empty, all offers will be retrieved. The endpoint uses incrementing page number pagination to handle large datasets efficiently, returning up to 100 records per page by default.
This endpoint returns offers filtered by status from your Tune Network account, including offer IDs, names, status, and other offer metadata. The endpoint uses incrementing page number pagination with page and limit parameters to handle large datasets efficiently. Nexla will automatically follow the pagination to fetch subsequent pages of data.
For detailed information about offers, API response structures, pagination, and available offer data, see the Tune Network 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.
Tune Network data sources can also be manually configured to ingest data from any valid Tune Network API endpoint, including endpoints not covered by the pre-built templates, chained API calls to fetch data from multiple endpoints, or custom authentication headers or request parameters. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, endpoint URL, date/time and lookup macros, path to data, metadata, and request headers.
Tune Network API endpoint URLs follow the format https://{network_id}.api.hasoffers.com/Apiv3/json?Target={target}&Method={method}, where {network_id} is your Tune Network ID. Tune Network API responses typically return a top-level array containing the relevant data — enter $[*] as the Path to Data in Response for most endpoints.
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 Tune Network 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.
