Partnerize

Partnerize is a partner (affiliate) marketing management platform for tracking, attributing, and paying partner-driven transactions across a brand's partner network. This connector uses the Partnerize Partner API to ingest reference and reporting data and to manage partner tracking links and websites.

Power end-to-end data operations for your Partnerize API with Nexla. Our bi-directional Partnerize connector is purpose-built for Partnerize, 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 Partnerize or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Partnerize 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 Partnerize credential, you need a Partnerize Partner (Publisher) account and two keys issued by Partnerize: a User Application Key and a User API Key. The Partnerize API authenticates every request with HTTP Basic authentication, where the User Application Key is used as the username and the User API Key is used as the password.

To obtain your Partnerize credentials, follow these steps:

1. Sign in to the Partnerize console with your Partnerize account.

2. Open your Account settings from the account menu.

3. Locate the User Application Key and the User API Key in your account settings. The User Application Key identifies the network you are making requests against, and the User API Key identifies the user on whose behalf the request is made.

4. Copy both keys and store them securely. You will provide the User Application Key as the Username and the User API Key as the Password when creating your Nexla credential.

Partnerize combines the two keys as application_key:user_api_key, Base64-encodes the pair, and sends it in the Authorization: Basic header on every request. If your keys are compromised, regenerate them from your Partnerize account settings. For detailed information about authentication and available endpoints, see the Partnerize Partners API documentation.

Authenticate

Credentials required

Field	Required	Secret	Description
Username	Yes	No	Username used to authenticate requests to the Partnerize API.
Password	Yes	Yes	Password used to authenticate requests to the Partnerize API.

For Partnerize, enter your User Application Key in the Username field and your User API Key in the Password field. Both keys are found in your Partnerize account settings.

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.

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 Partnerize User Application Key in the Username field.

4. Enter your Partnerize User API Key in the Password field. This value is sensitive and must be kept confidential.

5. 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 Partnerize connector tile, then select the credential that will be used to connect to Partnerize, and click Next; or, create a new Partnerize 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 Partnerize 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.

[Rest API] List User Context

This endpoint template retrieves user context from the Partnerize Partner API. Use this template when you need to access the user context available to your account.

This endpoint returns paginated results. Nexla automatically follows pagination to fetch subsequent pages of data. For detailed information about response structures and available fields, see the Partnerize Partners API documentation.

[Rest API] List Conversion Metrics

This endpoint template retrieves conversion metrics from the Partnerize Partner API. Use this template when you need to access conversion metric reference data.

This endpoint returns paginated results. Nexla automatically follows pagination to fetch subsequent pages of data. For detailed information about response structures and available fields, see the Partnerize Partners API documentation.

[Rest API] List Countries

This endpoint template retrieves the list of countries from the Partnerize Partner API. Use this template when you need country reference data for enrichment or lookups.

This endpoint returns a static reference list. For detailed information about response structures and available fields, see the Partnerize Partners API documentation.

[Rest API] List Currencies

This endpoint template retrieves the list of currencies from the Partnerize Partner API. Use this template when you need currency reference data for enrichment or lookups.

This endpoint returns a static reference list. For detailed information about response structures and available fields, see the Partnerize Partners API documentation.

[Rest API] List Devices

This endpoint template retrieves the list of devices from the Partnerize Partner API. Use this template when you need device reference data for enrichment or lookups.

This endpoint returns a static reference list. For detailed information about response structures and available fields, see the Partnerize Partners API documentation.

[Rest API] List Timezones

This endpoint template retrieves the list of timezones from the Partnerize Partner API. Use this template when you need timezone reference data for enrichment or lookups.

This endpoint returns a static reference list. For detailed information about response structures and available fields, see the Partnerize Partners API documentation.

[Rest API] List Traffic Sources

This endpoint template retrieves the list of traffic sources from the Partnerize Partner API. Use this template when you need traffic source reference data for enrichment or lookups.

This endpoint returns a static reference list. For detailed information about response structures and available fields, see the Partnerize Partners API documentation.

[Rest API] List Conversion Type

This endpoint template retrieves conversion types from the Partnerize Partner API. Use this template when you need conversion type reference data.

This endpoint returns paginated results. Nexla automatically follows pagination to fetch subsequent pages of data. For detailed information about response structures and available fields, see the Partnerize Partners API documentation.

[Rest API] List Partnership Model

This endpoint template retrieves partnership models from the Partnerize Partner API. Use this template when you need partnership model reference data.

This endpoint returns paginated results. Nexla automatically follows pagination to fetch subsequent pages of data. For detailed information about response structures and available fields, see the Partnerize Partners 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

Partnerize data sources can also be manually configured to ingest data from any valid Partnerize Partner API endpoint, including endpoints not covered by the pre-built templates, chained API calls, or custom 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.

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 Partnerize 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.

Use as a destination

Click the + icon on the Nexset that will be sent to the Partnerize destination, and select the Send to Destination option from the menu. Select the Partnerize connector from the list of available destination connectors, then select the credential that will be used to connect to Partnerize, and click Next; or, create a new Partnerize credential for use in this flow.

Endpoint templates

Nexla provides pre-built templates that can be used to rapidly configure destinations to send data to common Partnerize endpoints. Select the endpoint to which data will be sent from the Endpoint pulldown menu. Then, click on the template in the list below to expand it, and follow the instructions to configure additional endpoint settings.

[Rest API] Create Tracking Link

This endpoint template creates a new partner tracking link for a campaign using records from a Nexset. Use this template when you need to programmatically generate tracking links from your Nexla flows.

This endpoint sends each record as a JSON request body to create a new tracking link. Ensure your records include the fields required by the Partnerize tracking-links API. For detailed information about request body formats and available properties, see the Partnerize Partners API documentation.

[Rest API] Update Tracking Link

This endpoint template updates an existing partner tracking link by ID using records from a Nexset. Use this template when you need to modify tracking links that already exist in Partnerize.

• This template requires a Tracking Link ID parameter — the ID of the tracking link to update. Provide this value when configuring the endpoint so Nexla can construct the request URL.

This endpoint sends each record as a JSON request body to update the specified tracking link. For detailed information about request body formats and available properties, see the Partnerize Partners API documentation.

[Rest API] Create Partner Website

This endpoint template creates one or more websites against the partner entity using records from a Nexset. Use this template when you need to register partner websites from your Nexla flows.

This endpoint sends each record as a JSON request body to create partner websites. Ensure your records include the fields required by the Partnerize websites API. For detailed information about request body formats and available properties, see the Partnerize Partners API documentation.

Manual configuration

Partnerize destinations can also be manually configured to send data to any valid Partnerize API endpoint. 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, data format, endpoint URL, request headers, attribute exclusions, record batching, and response webhooks.

Save & activate

Once all endpoint settings have been configured, click the Done button in the upper right corner of the screen to save and create the destination. To send the data to the configured Partnerize endpoint, open the destination resource menu, and select Activate.

The Nexset data will not be sent to the Partnerize endpoint until the destination is activated. Destinations can be activated immediately or at a later time, providing full control over data movement.