Skip to main content

AWIN Advertiser

Awin is a global affiliate marketing network that connects advertisers with publishers to drive performance-based marketing programs. The AWIN Advertiser API enables programmatic access to campaign performance data, publisher relationships, and transaction history, allowing advertisers to automate reporting, validate transactions in bulk, and submit proof-of-purchase events for affiliate programs.

AWIN Advertiser icon

Power end-to-end data operations for your AWIN Advertiser API with Nexla. Our bi-directional AWIN Advertiser connector is purpose-built for AWIN Advertiser, 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 AWIN Advertiser or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your AWIN Advertiser 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​

The AWIN Advertiser API uses OAuth 2.0 bearer token authentication. The access token is generated from the Awin user interface and is linked to your personal user account—it grants access to data for every advertiser account that your user can manage on the Awin platform.

Awin Account Requirements​

  • An active Awin advertiser account is required to use this connector. Advertiser APIs are only available to advertisers on the Awin Accelerate or Advanced plans, so confirm that your account is on a supported plan before proceeding.

  • Note your Advertiser ID before configuring data flows. This numeric identifier is required by most endpoints and can be found in the Awin advertiser dashboard URL or under your account profile.

  • Awin enforces a throttling limit of 20 API calls per minute per user. Plan ingestion frequency and pagination settings accordingly to avoid rate-limit errors.

Generate Your AWIN API Token​

  1. Sign in to the Awin platform at https://ui.awin.com using your Awin username and password.

  2. Open the API Credentials page directly, or click your user menu in the top-right corner and select API Credentials.

  3. On the API Credentials page, enter the password that you use to log in to the Awin website in the password field.

  4. Click the Show my API token button. Your personal API token will be generated and displayed on the page.

  5. Copy the displayed token value to your clipboard. You will paste this raw token into Nexla when creating the credential—do not include any prefix such as Bearer when copying, since Nexla adds the prefix automatically.

    Your API token is tied to your individual user account, not to a specific advertiser. The token grants access to data for every advertiser account that your user can manage on the Awin platform. If the token is ever compromised, return to the API Credentials page, enter your password, and click Revoke my API token to invalidate it and generate a new one.

For additional reference, see the Awin API authentication documentation and the Awin APIs overview.

Authenticate​

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. Paste the API token that you generated from the Awin API Credentials page into the API Key Value field. Enter only the raw token value—do not prepend Bearer to the token, because Nexla automatically adds the Bearer prefix when calling the standard Awin endpoints and reuses the same value as the x-api-key header for the proof-of-purchase submission endpoint.

    Treat the API token like a password. Anyone with this token can read and modify data for every advertiser account your Awin user can access. Store it only in secure credential systems, and rotate it from the Awin API Credentials page if you suspect it has been exposed.

  4. Click the Save button at the bottom of the overlay to save the configured credential. The newly added credential will now appear in a tile on the Authenticate screen during data source/destination creation and can be selected for use with a new data source or destination.

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 AWIN Advertiser connector tile, then select the credential that will be used to connect to the AWIN Advertiser instance, and click Next; or, create a new AWIN Advertiser 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 AWIN Advertiser 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. Click on an endpoint to see more information about it and how to configure your data source for this endpoint.

Get Campaign Performance

This endpoint retrieves campaign performance metrics and statistics for the advertiser from the /advertisers/{'{advertiserId}'}/reports/campaign endpoint. Use this template when you need a paginated snapshot of campaign-level performance data without specifying a date window.

  • Enter your unique advertiser account identifier in the Advertiser ID field. This numeric ID is required and can be found in the URL of your Awin advertiser dashboard or under your account profile.
  • The Page field controls the starting page number for pagination. The default value of 1 is appropriate for most ingestion scenarios.
  • The Page Size field controls the number of records returned per page. The default value of 100 aligns with Awin's expected page size; lower values can be used when testing.

Pagination automatically advances pages until an empty response is returned, so leaving the page and page size fields at their defaults is sufficient for most full-history ingestion runs.

Get Advertiser Campaign Report

This endpoint retrieves aggregated campaign performance data (clicks and transactions) by campaign and publisher for a specified date window. Use this template for time-bounded reporting and to break down campaign performance over daily, weekly, or monthly intervals.

  • Enter your Awin advertiser account ID in the Advertiser Id field.
  • Enter the report period start date in the Start Date field using the format YYYY-MM-DD (for example, 2026-01-01).
  • Enter the report period end date in the End Date field using the format YYYY-MM-DD.
  • Enter the timezone used for date calculations in the Timezone field (for example, UTC or America/New_York). This controls how Awin bucketizes daily, weekly, and monthly intervals.
  • Enter the date field used for filtering in the Date Type field. Common values are transaction (default in Awin) and click.
  • Enter the aggregation interval in the Interval field. Supported values are daily, weekly, and monthly.
  • Leave the Page and Page Size fields at their defaults (1 and 100) unless a smaller test batch is needed.

Awin returns up to a maximum date range per call—check the Get Campaign Performance API reference for current limits. For long historical pulls, split the ingestion into multiple date windows.

Get Publisher Performance Report

This endpoint retrieves aggregated performance metrics—transactions, clicks, and impressions—for every publisher that your advertiser program works with. Use this template to analyze publisher contribution and to benchmark performance across regions.

  • Enter your Awin advertiser account ID in the Advertiser Id field.
  • Enter the start and end of the report period in the Start Date and End Date fields using YYYY-MM-DD format.
  • Enter the timezone used for date calculations in the Timezone field (for example, UTC).
  • Enter the date field used for filtering in the Date Type field (commonly transaction or click).
  • Enter an optional publisher region filter in the Region field to scope the report to a specific market (for example, US or UK). Leave blank to include all regions.
  • Leave the Page and Page Size fields at the defaults of 1 and 100 for full-result ingestion.

The publisher report aggregates across the entire advertiser program. To track changes over time, schedule recurring ingestion runs with rolling date windows rather than a single one-off pull.

Get Advertiser Transaction Job by ID

This endpoint retrieves the status and error details for a single bulk transaction validation job. Use this template after submitting a batch validation request to check whether the job completed successfully or to inspect rejection reasons.

  • Enter your Awin advertiser account ID in the Advertiser Id field.
  • Enter the unique job identifier returned by Awin when the validation job was created in the Job Id field.

Use the Get Advertiser Transaction Jobs endpoint to retrieve a paginated list of recent job IDs if the original job ID is not readily available.

Get Advertiser Transactions by IDs

This endpoint retrieves individual transactions for a given advertiser, filtered by a list of transaction IDs. Use this template to pull a targeted set of transactions for reconciliation, validation, or downstream enrichment.

  • Enter your Awin advertiser account ID in the Advertiser Id field.
  • Enter a comma-separated list of transaction IDs to retrieve in the Transaction IDs field (for example, 123456,123457,123458).
  • Enter the timezone for transaction dates in the Timezone field (for example, UTC).
  • Set the Show Basket Products field to true to include the basket-level product detail for each transaction. Leave blank or set to false to receive transaction summaries only.

Returning basket products can significantly increase the response payload size. Enable this option only when product-level reporting is required.

Get Accounts

This endpoint retrieves the list of advertiser accounts accessible to the authenticated user from the /accounts?type=advertiser endpoint. Use this template to discover the Advertiser IDs that your API token can access before configuring other endpoints.

  • This endpoint requires no additional configuration. Select the template and click Test to retrieve the list of advertiser accounts visible to your API token.

Use the accountId values returned from this endpoint as the Advertiser ID input for the campaign, publisher, and transaction endpoints.

Get Advertiser Publishers

This endpoint retrieves the list of publishers with active relationships for the given advertiser, including region and promotion type information. Use this template to maintain an up-to-date directory of partner publishers for your program.

  • Enter your Awin advertiser account ID in the Advertiser Id field.
  • The endpoint uses offset-based pagination internally and will automatically fetch additional pages until no more publishers are returned.

Schedule this ingestion on a daily or weekly cadence to keep downstream publisher dimensions current as new partnerships are added or paused.

Get Advertiser Transaction Jobs

This endpoint retrieves bulk transaction validation job statuses for the given advertiser. Use this template to monitor the queue of validation jobs that you have submitted and to surface jobs that completed with errors.

  • Enter your Awin advertiser account ID in the Advertiser Id field.
  • Offset-based pagination automatically advances through the list of jobs until the API returns no further results.

Combine the results of this endpoint with Get Advertiser Transaction Job by ID to programmatically inspect the success or failure of each batch validation request.

List Transactions

This endpoint retrieves a list of transactions for the advertiser account, filtered by date range. Use this template for incremental ingestion of transaction-level affiliate data into your warehouse or downstream attribution platform.

  • Enter your Awin advertiser account ID in the Advertiser ID field.
  • Enter the start of the date window in the Start Date field using the ISO datetime format yyyy-MM-ddTHH:mm:ss.
  • Enter the end of the date window in the End Date field using the ISO datetime format yyyy-MM-ddTHH:mm:ss.
  • Enter the date field used for filtering in the Date Type field. Supported values are transaction (default), click, and validation.
  • Enter the timezone for date filtering in the Timezone field. Defaults to UTC.
  • Leave Page Number and Page Size at the defaults to use the standard 100-record pagination, or override them if smaller test batches are needed.

Awin enforces a maximum window of 31 days per request for the transactions endpoint. For longer ranges, schedule recurring runs that step through 31-day windows.

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​

AWIN Advertiser data sources can also be manually configured to ingest data from any valid AWIN Advertiser API endpoint, including endpoints not covered by the pre-built templates, sources that chain calls between the accounts, publishers, and transactions endpoints, 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.

All Awin Advertiser endpoints are hosted under the base URL https://api.awin.com; the full endpoint list is documented at help.awin.com/apidocs. Awin wraps result records in a top-level object, so set the Path to Data accordingly—for example, $.result[*] (Campaign Performance), $.report[*] (campaign and publisher reports), $.accounts[*] (Accounts), $.publishers[*] (Publishers), $.jobs[*] (transaction jobs), or $[*] (List Transactions and Get Transactions by IDs).

For date/time macros, use the ISO datetime format yyyy-MM-dd'T'HH:mm:ss for the transaction endpoints and yyyy-MM-dd for the report endpoints. You do not need to add an Authorization header—Nexla automatically applies the Authorization: Bearer ... header based on the configured credential. Awin enforces a throttling limit of 20 API calls per minute per user account; repeated 429 Too Many Requests responses indicate that the limit has been exceeded.

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 AWIN Advertiser 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 AWIN Advertiser destination, and select the Send to Destination option from the menu. Select the AWIN Advertiser connector from the list of available destination connectors, then select the credential that will be used to connect to the AWIN Advertiser organization, and click Next; or, create a new AWIN Advertiser 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 AWIN Advertiser 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.

Submit Proof-of-Purchase Publisher Transaction

This endpoint submits proof-of-purchase transactions from a CLO (Card-Linked Offer) publisher directly to an advertiser's program. Use this template to push completed order data into Awin in batches of up to 1,000 orders per call.

  • Enter your Awin advertiser account ID in the Advertiser Id field. This ID is used as a path parameter against the server-to-server endpoint {'POST https://api.awin.com/s2s/advertiser/{advertiserId}/orders'}.
  • Each record sent from Nexla must conform to Awin's proof-of-purchase order schema. Review the Awin S2S documentation for the exact field structure expected for each order.
  • This endpoint uses the x-api-key header for authentication, which Nexla populates automatically from the API token stored in the configured credential.

Awin accepts up to 1,000 orders per request on this endpoint. Configure the Record Batching settings in the Advanced tab if you need to chunk a larger payload into compliant batches.

Validate Advertiser Transactions

This endpoint approves, declines, or amends a batch of transactions for the given advertiser by sending a PATCH request to {'/advertisers/{advertiserId}/transactions'}. Use this template to programmatically validate Awin transactions based on internal order, fraud, or returns data.

  • Enter your Awin advertiser account ID in the Advertiser Id field.
  • Each Nexset record sent to this endpoint should contain the transaction ID along with the new status (approve, decline, or amend) and any supporting fields, formatted according to Awin's transaction validation schema.
  • Awin executes validation asynchronously: a successful response returns a job identifier that can be inspected with the Get Advertiser Transaction Job by ID source endpoint.

Combine this destination with the Get Advertiser Transaction Jobs source endpoint to monitor validation outcomes and surface any rejected records for re-processing.

Manual configuration​

AWIN Advertiser destinations can also be manually configured to send data to any valid AWIN Advertiser API endpoint, and can automatically forward the API response after each call to a new Nexla webhook data source—useful for capturing the asynchronous job IDs returned by the validate-transactions 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.

Awin write endpoints are hosted at https://api.awin.com and expect application/json payloads. Use POST to submit proof-of-purchase orders to {'https://api.awin.com/s2s/advertiser/{advertiserId}/orders'}, or PATCH to approve, decline, or amend transactions at {'https://api.awin.com/advertisers/{advertiserId}/transactions'}. You do not need to add authentication headers—Nexla automatically applies the Authorization: Bearer ... header for the validate endpoint and the x-api-key header for the S2S proof-of-purchase endpoint.

Awin enforces a throttling limit of 20 API calls per minute per user account, and the proof-of-purchase endpoint accepts up to 1,000 orders per request. Enable Record Batching to consolidate records into compliant batches—set the batch size at or below 1,000 for the S2S endpoint—rather than firing one call per record.

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 AWIN Advertiser endpoint, open the destination resource menu, and select Activate.

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