Dixa is a conversational customer service platform that enables real-time dialogs between businesses and their clients over voice, email, social media, and messaging. The Dixa platform enables businesses to improve customer relationships by integrating all customer data and communication channels.

Dixa authenticates API requests from Hevo to access your account data with HTTP Basic authentication.


  • An active Dixa account from which data is to be ingested.

  • The API Token is available to authenticate Hevo on your Dixa account.

  • You are logged in as an Admin user, to obtain the API token. Else, you can obtain the API token from your administrator. Read User Types to know about the different types of user accounts in Dixa.

Obtaining the API Token

Hevo uses an API token to authenticate itself on your Dixa account.

Perform the following steps to create the access token:

  1. Log in to your Dixa account.

  2. In the left navigation pane, click Settings, and select Integrations from the drop-down.


  3. In the Integrations page, click Configure API tokens from the API Tokens card.

    Configure API token

  4. In the API Tokens page, do one of the following:

    • Create an API Token:

      1. Click Add API Token.

        Add API Token

      2. In the Create new token page, specify a unique name for this API Token, and click Save.

        Specify Name

      3. Click the Copy icon to copy the API Token and save it securely like any other password.

        Copy API token

    • Use an existing API Token:

      View API Token

      1. Click the View ( overview image ) icon corresponding to the name of the API Token, to reveal the API Token.

      2. Copy the API token and save it securely like any other password.

You have successfully obtained your API token. Use this token for creating Hevo Pipelines.

Configuring Dixa as a Source

Perform the following steps to configure Dixa as the Source in your Pipeline:

  1. Click PIPELINES in the Asset Palette.

  2. Click + CREATE in the Pipelines List View.

  3. In the Select Source Type page, select Dixa.

  4. In the Configure your Dixa Source page, specify the following:

    Source config

    • Pipeline Name: A unique name for the Pipeline, not exceeding 255 characters.

    • API Token: The API Token that you obtained and copied from your Dixa account.

  5. Click TEST & CONTINUE.

  6. Proceed to configuring the data ingestion and setting up the Destination.

Data Replication

Default Pipeline Frequency Minimum Pipeline Frequency Maximum Pipeline Frequency Custom Frequency Range (Hrs)
1 hr 1 hr 24 hrs 1-24

Note: You must set the custom frequency in hours as an integer value. For example, 1, 2, 3 but not 1.5 or 1.75.

  • Historical Data: In the first run of the Pipeline, Hevo ingests all historical data for the Conversations and Messages objects and loads it to the Destination.

  • Incremental Data: Once the historical load is complete, all new and updated records for the Conversations and Messages objects are synchronized with your Destination as per the Pipeline frequency.

Source Considerations

  • Rate Limit: Dixa imposes a limit of a maximum of 10 API calls per second per account to optimize performance.

Schema and Primary Keys

Hevo uses the following schema to upload the records in the Destination database:

Data Model

The following is the list of tables (objects) that are created at the Destination when you run the Pipeline:

Object Description
Conversations Contains the details of all the replies as well as notes added to a ticket. Notes are non-invasive ways of sharing updates about a ticket amongst agents and customers.
Messages Contains the details of the messages sent and received from the customers such as the sender name and email address.


  • Hevo currently does not support deletes. Therefore, any data deleted in the Source may continue to exist in the Destination.

  • The data is loaded in Incremental Load in each Pipeline run. As a result, you cannot load the historical data alone at any time.

Revision History

Refer to the following table for the list of key updates made to this page:

Date Release Description of Change
Sep-09-2022 1.97 New document.
Last updated on 13 Sep 2022

Tell us what went wrong