Linkrunner

Linkrunner is a mobile attribution and deep-linking platform that helps app marketers measure where installs and conversions come from. Its API provides access to campaigns, attributed users, attribution results, and revenue events, and lets you create and manage campaigns and short links programmatically.

Power end-to-end data operations for your Linkrunner API with Nexla. Our bi-directional Linkrunner connector is purpose-built for Linkrunner, 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 Linkrunner or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Linkrunner 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 Linkrunner credential, you need a Linkrunner account and an API key. Linkrunner authenticates all API requests with an API key that is sent in the linkrunner-key request header.

To obtain your Linkrunner API key, follow these steps:

1. Sign in to your Linkrunner account at dashboard.linkrunner.io.

2. Navigate to Settings, then open the Data APIs section (available directly at dashboard.linkrunner.io/settings?s=data-apis).

3. Copy the API key shown for your workspace. This is the value that Nexla sends in the linkrunner-key header for every request.

4. Store the API key securely. Treat it as a secret, and make API requests only from a secure server-side environment. If the key is ever exposed, generate a new one from the same Settings page.

The default base URL for the Linkrunner API is https://api.linkrunner.io. For complete details about authentication and available endpoints, see the Linkrunner API reference.

Authenticate

Credentials required

Field	Required	Secret	Description
API Key Value	Yes	Yes	An encoded string value used as a secret token to authenticate API requests
Base URL	Yes	No	The root URL for Linkrunner API endpoints. Adjust for environment (production, sandbox, etc.).

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 Linkrunner API key in the API Key Value field. This is the key you obtained in Prerequisites, and it is sent in the linkrunner-key header for all API requests. This value is stored securely and must be kept confidential.

4. Enter the Linkrunner API root URL in the Base URL field. The default is https://api.linkrunner.io; adjust it only if you are targeting a different environment.

   If your API key is compromised, generate a new one from the Data APIs section of your Linkrunner Settings and update this credential. The API key grants access to your Linkrunner workspace data and should be treated as sensitive information.

   For detailed information about authentication and available endpoints, see the Linkrunner API reference.

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

Returns a list of all campaigns in the Linkrunner account.

• This endpoint retrieves all campaigns accessible to your API key. Results are paginated, and Nexla automatically iterates through the pages to fetch the complete set of campaigns.

For detailed information about campaign fields and response structures, see the Linkrunner Campaign APIs documentation.

[Rest API] List Campaigns (Filtered)

List all campaigns for the authenticated account.

• This endpoint returns campaigns for the authenticated account and supports optional filters, including status (ACTIVE, INACTIVE, ALL), channel, domain, and a specific link. Results are paginated, and Nexla automatically iterates through the pages.

For detailed information about the available filters and response structures, see the Linkrunner Campaign APIs documentation.

[Rest API] Get Campaign by ID

Retrieve details for a single campaign by ID.

• This endpoint returns the full details for one campaign. Provide the campaign's unique identifier in the required Campaign Id field.

For detailed information about campaign fields, see the Linkrunner Campaign APIs documentation.

[Rest API] Fetch Attributed Users

Fetch attributed users with campaign attribution data.

• This endpoint returns users attributed to a campaign, along with their attribution data. Provide the campaign's Display ID (required), and optionally narrow results with start and end timestamps (ISO 8601), a timezone (IANA string, default UTC), and pagination controls. Nexla automatically iterates through the pages.

For detailed information about attributed-user fields and response structures, see the Linkrunner Data APIs documentation.

[Rest API] Get Attribution Result

Retrieve attribution data for a specific user or device. Returns campaign and ad network information for attributed installs.

• This endpoint looks up the attribution result for a single user or device. Provide a Device Identifier (GAID on Android or IDFA on iOS) and/or a User ID — at least one of the two is required.

For detailed information about attribution results and response structures, see the Linkrunner Data APIs documentation.

[Rest API] Get Account Info

Retrieve authenticated account / workspace info.

• This endpoint returns information about the account and workspace associated with the API key used in the credential. It is useful for verifying that a credential is configured correctly.

For detailed information about the account response, see the Linkrunner Data APIs 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

Linkrunner data sources can also be manually configured to ingest data from any valid Linkrunner 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 Linkrunner 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 Linkrunner destination, and select the Send to Destination option from the menu. Select the Linkrunner connector from the list of available destination connectors, then select the credential that will be used to connect to Linkrunner, and click Next; or, create a new Linkrunner 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 Linkrunner 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 a Campaign

Create a new campaign. Optionally create a short link by including the is_shortlink: true parameter.

• This endpoint sends each record from your Nexset as a JSON request body to create a new campaign in Linkrunner. Include is_shortlink: true in the record to also generate a short link for the campaign.

The request body must match the format required by the Linkrunner API. For detailed information about campaign creation and request body fields, see the Linkrunner Campaign APIs documentation.

[Rest API] Update a Campaign

Update an existing campaign's settings or metadata.

• This endpoint sends each Nexset record as a JSON request body to update an existing campaign. Provide the campaign's unique identifier in the required Campaign Id field to identify the campaign to update.

The request body must match the format required by the Linkrunner API. For detailed information about updatable campaign fields, see the Linkrunner Campaign APIs documentation.

[Rest API] Delete a Campaign

Delete an existing campaign.

• This endpoint deletes an existing campaign. Provide the campaign's unique identifier in the required Campaign Id field to identify the campaign to delete.

Deleting a campaign is permanent. For detailed information about campaign deletion, see the Linkrunner Campaign APIs documentation.

[Rest API] Capture Payment

Records a payment transaction for an attributed user for revenue tracking.

• This endpoint sends each Nexset record as a JSON request body to record a payment transaction for an attributed user, enabling revenue attribution and reporting in Linkrunner.

The request body must match the format required by the Linkrunner API. For detailed information about revenue tracking and payment fields, see the Linkrunner Revenue Tracking documentation.

Manual configuration

Linkrunner destinations can also be manually configured to send data to any valid Linkrunner 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.

Linkrunner APIs expect JSON format for write operations. For update and delete operations, include the campaign ID required by the endpoint.

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

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