Dixa

Last updated on Jul 03, 2025

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.


Source Considerations

  • Rate Limit: Dixa imposes a limit of 10 API calls per second per account. If the limit is exceeded, Hevo defers the ingestion till the limits reset.

Limitations

  • 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.

  • Hevo does not load data from a column into the Destination table if its size exceeds 16 MB, and skips the Event if it exceeds 40 MB. If the Event contains a column larger than 16 MB, Hevo attempts to load the Event after dropping that column’s data. However, if the Event size still exceeds 40 MB, then the Event is also dropped. As a result, you may see discrepancies between your Source and Destination data. To avoid such a scenario, ensure that each Event contains less than 40 MB of data.


Revision History

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

Date Release Description of Change
Jul-07-2025 NA Updated the Limitations section to inform about the max record and column size in an Event.
Jan-07-2025 NA Updated the Limitations section to add information on Event size.
Mar-05-2024 2.21 Updated the ingestion frequency table in the Data Replication section.
Oct-03-2023 NA Updated the section, Obtaining the API Token as per the latest Dixa UI.
Sep-09-2022 1.97 New document.

Tell us what went wrong