> AI agents: this is one page from PostHog's docs. Full index of Markdown docs for LLMs: https://posthog.com/llms.txt

# Linking DingConnect as a source

Canonical URL: https://posthog.com/docs/data-pipelines/sources/ding-connect

> **Cloud region:** This page uses US Cloud hosts. For an EU Cloud project, use `https://eu.posthog.com` instead of `https://us.posthog.com` or `https://app.posthog.com` (app host for links).

## On this page

- [Prerequisites](#prerequisites)
- [Adding a data source](#adding-a-data-source)
- [Sync modes](#sync-modes)
- [Configuration](#configuration)
- [Supported tables](#supported-tables)
- [Troubleshooting](#troubleshooting)

**Beta release**

This source is currently in **beta**. It works end to end, but you may still hit rough edges. [Let us know](https://us.posthog.com/#panel=support%3Asupport%3Adata_warehouse%3A%3Atrue) if you do.

![](https://res.cloudinary.com/dmukukwp6/image/upload/texture_tan_9608fcca70)

![](https://res.cloudinary.com/dmukukwp6/image/upload/texture_tan_dark_a92b0e022d)

Let AI connect your sources for you

Skip the manual setup — run this in your project and the wizard auto-detects your databases and APIs and connects them to PostHog.

`npx @posthog/wizard warehouse`

![PostHog Wizard hedgehog](https://res.cloudinary.com/dmukukwp6/image/upload/wizard_3f8bb7a240.png)

![](https://res.cloudinary.com/dmukukwp6/image/upload/wizard_3f8bb7a240.png)Let AI connect your sources for you

The DingConnect connector syncs your DingConnect data into the PostHog Data warehouse, so you can analyze your top-up transactions and account balances alongside your product data.

## Prerequisites

You need a DingConnect account with API access so you can generate an API key.

## Adding a data source

1.  In PostHog, go to the [Sources tab](https://app.posthog.com/data-management/sources) of the data pipeline section.
2.  Click **\+ New source** and click **Link** next to this source.
3.  Enter your credentials (see [Configuration](#configuration) below) and click **Next**.
4.  Select the tables you want to sync, choose a sync method and frequency, then click **Import**.

Once the syncs are complete, you can start querying this data in PostHog.

When linking DingConnect, you'll need:

-   **API key** – generate one under the **Developer** tab of your [DingConnect account settings](https://www.dingconnect.com/Account/Settings).

## Sync modes

Each table can be synced in one of several modes, depending on what the source supports:

-   **Webhook** (when available) – the source pushes changes to PostHog in real time. Fastest freshness, lowest ongoing cost, and the only mode that reliably captures updates and deletes.
-   **Incremental** – only new or updated rows are synced on each run, using a cursor field (such as an `updated_at` timestamp). Cheaper than a full refresh, but deletes aren't captured.
-   **Append only** – new rows are appended using a cursor field; existing rows are never updated. Ideal for immutable, append-only tables like event logs.
-   **Full refresh** – the whole table is reloaded on every sync. Use it when a table has no reliable cursor or when you need deletions reflected.

See [sync methods](https://posthog.com/docs/data-pipelines/sources.md#sync-methods) for a full explanation of how each mode works and how to choose between them.

All DingConnect tables are full refresh only, since the API exposes no incremental sync filter.

## Configuration

| Option | Type | Required |
| --- | --- | --- |
| `API key` | password | Yes |

## Supported tables

| Table | Description | Sync method | Incremental field | Primary key |
| --- | --- | --- | --- | --- |
| `Countries` | A country that DingConnect operates in. | Full refresh | — | — |
| `Currencies` | A currency that DingConnect supports. | Full refresh | — | — |
| `Regions` | A region within a country. A provider may only service a subset of a country's regions, and a product may only be valid for a subset. | Full refresh | — | — |
| `Providers` | A mobile operator or biller whose products can be sold through DingConnect. | Full refresh | — | — |
| `ProviderStatus` | Whether each provider can currently accept transfers. Providers can be suspended or in an error state. | Full refresh | — | — |
| `Products` | A sellable product (e.g. a top-up amount) offered by a provider. | Full refresh | — | — |
| `ProductDescriptions` | Localized long-form product text, keyed by the LocalizationKey carried on each product. Large blocks of text are CommonMark. | Full refresh | — | — |
| `Promotions` | A time-bound promotion applied to a provider's products. | Full refresh | — | — |
| `Balance` | Current account balance per currency. Full refresh only | Full refresh | — | — |
| `ErrorCodeDescriptions` | Human readable descriptions for the error codes returned in the ErrorCodes array of an API response. Aimed at the distributor rather than the end customer. | Full refresh | — | — |
| `TransferRecords` | Transfer history is only retained upstream for ~2 months. Full refresh only | Full refresh | — | — |

## Troubleshooting

-   If you get an authorization error, your DingConnect API key is invalid or has been revoked. Generate a new key under the **Developer** tab of your account settings, then reconnect.
-   If you get a permission error, your API key does not have access to this data. Check the key's permissions in your DingConnect account settings, then reconnect.

If your sync is failing or data looks wrong, see the [Data warehouse troubleshooting guide](https://posthog.com/docs/data-warehouse/troubleshooting.md). If that doesn't help, [contact support](https://us.posthog.com/#panel=support%3Asupport%3Adata_warehouse%3A%3Atrue) – we're happy to help.