AT Internet

AT Internet is a leading digital analytics platform that provides comprehensive web and mobile analytics solutions, offering detailed insights into user behavior, traffic analysis, and performance metrics for data-driven decision making.

Power end-to-end data operations for your AT Internet API with Nexla. Our bi-directional AT Internet connector is purpose-built for AT Internet, 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 AT Internet or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your AT Internet 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 an AT Internet credential in Nexla, you need to obtain your API key from your AT Internet account. This credential authenticates Nexla with the AT Internet Reporting API v3 and should be kept secure.

1. Sign in to your AT Internet account.

2. Navigate to Settings or Administration in your AT Internet account to access the settings page.

3. Locate the API or Developer section in the settings menu. This section contains your API credentials and access tokens.

4. Generate or copy your API Key. The API key is a secret token that authenticates API requests and provides access to your AT Internet account data. The API key is sent in the x-api-key header for all API requests.

   Your API key provides full access to your AT Internet account data through the Reporting API v3. Keep your API key secure and do not share it publicly or commit it to version control systems. If you suspect your API key has been compromised, regenerate it immediately in your AT Internet account settings. For detailed information about AT Internet API authentication, see the AT Internet API documentation.

Authenticate

Credentials required

Field	Required	Secret	Description
API Key Value	Yes	Yes	Your AT Internet API key, sent in the x-api-key header to authenticate with the AT Internet Reporting API v3.

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 – AT Internet

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 AT Internet API key in the API Key Value field. This key authenticates Nexla with the AT Internet Reporting API v3 and should match the API key obtained from your AT Internet account settings. The API key is sent in the x-api-key header for all API requests.

   The API key provides full access to your AT Internet account data through the API. Keep your API key secure and do not share it publicly or commit it to version control systems. AT Internet uses the API key in the x-api-key header for authentication, which allows Nexla to make authenticated requests to your account.

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

This endpoint retrieves analytics data from the AT Internet Reporting API v3. Use this endpoint when you need to access web analytics data, traffic metrics, or other reporting data from your AT Internet account.

• This endpoint uses POST requests to https://api.atinternet.io/v3/data/getData to retrieve analytics data from the AT Internet Reporting API v3. The endpoint requires a properly formatted JSON request body with the desired query parameters.
• Configure the request body in the manual configuration section to specify the metrics, dimensions, and date ranges you want to retrieve. The request body should follow the AT Internet API v3 format and include parameters such as space (site ID), period (date range), columns (metrics and dimensions), and optional filters.
• The endpoint supports date formatting with the format yyyy-MM-dd and uses days (dd) as the time unit for date operations. Date macros can be used in the request body to dynamically specify date ranges.
• The endpoint will return analytics data based on your query parameters. The response is returned at the root level of the JSON response, and Nexla will process the entire response structure.

This endpoint requires a properly formatted JSON request body with query parameters. The request body must be sent as the POST request body to the endpoint. The endpoint does not support pagination (isPaginated: false), so all matching data will be returned in a single response. The response structure is returned at the root level, and you may need to configure the Path to Data setting to extract the specific data you need from the response. Date formatting uses yyyy-MM-dd format with days as the time unit, which is useful for specifying date ranges in the period parameter. For detailed information about the AT Internet Reporting API v3, request body formatting, available parameters, and response structures, see the AT Internet API documentation.

Get Row Count

This endpoint retrieves the row count for a specific query from the AT Internet Reporting API v3. Use this endpoint when you need to determine the number of rows that would be returned by a query before executing the full data retrieval.

• This endpoint uses POST requests to https://api.atinternet.io/v3/data/getRowCount to retrieve row count information from the AT Internet Reporting API v3. The endpoint requires a properly formatted JSON request body with the desired query parameters.
• Configure the request body in the manual configuration section to specify the query parameters for which you want to retrieve the row count. The request body should follow the AT Internet API v3 format and include the same parameters you would use for the Get Data endpoint (space, period, columns, filters).
• The endpoint supports date formatting with the format yyyy-MM-dd and uses days (dd) as the time unit for date operations. Date macros can be used in the request body to dynamically specify date ranges.
• The endpoint will return the number of rows that match your query parameters. The response is returned at the root level of the JSON response, and this information can help you determine if you need to adjust your query or pagination settings before executing the full data retrieval.

This endpoint is useful for estimating data volume before executing full data retrieval queries. Like the Get Data endpoint, this endpoint requires a properly formatted JSON request body and does not support pagination. The request body should include the same parameters you would use for the Get Data endpoint (space, period, columns, filters) to get an accurate row count estimate. The response is returned at the root level of the JSON response. For detailed information about the AT Internet Reporting API v3 and request formatting, see the AT Internet 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

AT Internet data sources can also be manually configured to ingest data from any valid AT Internet 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.

The AT Internet Reporting API v3 uses POST requests to endpoints under the base https://api.atinternet.io/v3/data/ (for example, https://api.atinternet.io/v3/data/getData and https://api.atinternet.io/v3/data/getRowCount). Each call requires a JSON request body containing the query parameters — commonly space (site ID), period (date range), and columns (metrics and dimensions), with optional sort and filter. The endpoint does not support pagination, and the response is returned at the root level ($), so set the path to data accordingly. Date/time macros use the yyyy-MM-dd format with days (dd) as the time unit.

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 AT Internet 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.