Axiom

Overview

This Destination Connector sends data to Axiom via the Ingest data REST API.

Prerequisites

📘

Note: Each Tarsal Connector sends data to one Axiom Dataset

If using multiple datasets, then a separate Tarsal Destination connector should be created for each dataset. The same API key may be used for each connector.

1. The Destination Connector pushes data to a specific dataset.
   1. Note: It is recommended that the dataset be created prior to creating the API token, as the dataset access of the token can be restricted to said dataset. However, API tokens can be configured to send to all datasets in which case the dataset can be created after API Token creation.
2. Follow the steps to create an API token
   1. Under Token Permissions select Advanced
      1. In the All datasets table:
         1. Select the Ingest permission, and grant Create
         2. All other permissions should be unselected.
      2. Org level permissions
         1. None required
      3. Dataset Access
         1. Allow ingest to access a specific dataset. The dataset selected will be the Dataset Name used in the connector configuration below.
         2. If selecting multiple datasets, then you will need to create multiple Destination Connectors.

Configuration

Connector Limitations

1. This connector may be affected by API rate limits.
2. Depending on the pricing plan, ingest may be limited per month.