> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.joincandidhealth.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.joincandidhealth.com/_mcp/server.

# Set Up a Destination

> Have Candid deliver your Candid Data Share tables into a warehouse or database you own, set up in a few minutes from the Candid app

Candid Data Share delivers your tables straight into a warehouse or database you own. You set up the destination yourself in the Candid app, and Candid keeps it up to date every night. There's no pipeline for you to build or run.

## Before you start

* **Data Share must be turned on for your organization.** If it isn't, the Data Share page says *Data Share is not yet configured for your organization*. Email [support@joincandidhealth.com](mailto:support@joincandidhealth.com) or talk to your Candid account team to get started.
* **Each organization can set up a maximum of one destination.** If you need more than one destination, contact Candid.
* **You'll need two kinds of access:** a Candid login that can open **Settings & Integrations**, and permission in your warehouse or database to create a user and grant it access to a schema. This can be one person or two.

## Set up your destination

#### Prepare your warehouse or database

Follow the [setup guide for your destination type](#supported-destinations). Each guide lists exactly what to create and grant. In short:

1. **Create a place for the data.** Use a dedicated database and schema. Since Candid will create and update tables in it, don't reuse a schema to which your own team writes.
2. **Create a user or role for Candid** with permission to create and write tables in that schema.
3. **Allow Candid's IP addresses** if your destination restricts network access. See [below](#allow-candids-ip-addresses).

#### Add the destination in Candid

1. In the Candid app, navigate to **Settings & Integrations**, open the **Data Share** tab, and select **Data Share**.

   ![The Data Share tab in Settings & Integrations](/_fern-files/_img/1ba6f61b492751a33e2fb159f2cc1264e602c13ad8328693ab3399d9cca4bf11.webp)

2. Select **Create**.

3. Enter a **Destination name**, such as `Snowflake production`, and choose your destination type.

   ![The destination form with Snowflake selected](/_fern-files/_img/b1571c1fbdcb3f4bc24516c50929d2e0d4fe4c814617a55aca04ea0508264b5c.webp)

4. Fill in the connection details. The fields depend on the destination type. For Snowflake, for example, you'll enter the host, database, schema and user. Anything your setup guide says is provided to you, such as a public key, a service account or a trust policy, is shown in the form.

5. Select **Test connection**. Candid checks that it can reach your destination and write to it. If the test fails, check the details against your setup guide and try again.

6. Select **Create destination**.

#### Wait for your first delivery

Candid delivers to your destination every night. The first delivery sends all of your available data, so it can take longer than later ones. After that, each delivery sends only rows that are new or changed.

Until the first delivery finishes, the destination's **Last transfer** shows *No successful sync yet*.

#### Confirm your data has arrived

When **Last transfer** shows a date, check that the tables have rows and that the latest change is recent:

```sql
SELECT 'export_encounter' AS table_name, COUNT(*) AS row_count, MAX(_cds_row_version) AS latest_change FROM export_encounter
UNION ALL
SELECT 'export_service_line', COUNT(*), MAX(_cds_row_version) FROM export_service_line
UNION ALL
SELECT 'export_transaction', COUNT(*), MAX(_cds_row_version) FROM export_transaction
```

Every table should have rows, and `latest_change` should fall within the last day. To spot-check a record, look up an `encounter_id` you know from Candid in `export_encounter`.

## Allow Candid's IP addresses

If your warehouse or database only accepts connections from approved IP addresses, allow both of these:

| IP address         |
| ------------------ |
| `34.42.32.108/32`  |
| `34.70.167.173/32` |

Allow both, even if Candid connects from only one of them today, so delivery keeps working if Candid's network changes.

## How delivery works

* **One table for each Candid Data Share table**, with the same names, columns and primary keys as in these docs.
* **Rows are updated in place on the primary key.** Each delivery updates changed rows and adds new ones, so there's nothing to deduplicate.
* **New columns are added automatically.** Select columns by name instead of relying on column order.
* **Data is delivered once a night.**

## Check on your deliveries

The **Destinations** table on the Data Share page shows your destination's type, status, sync frequency, and when its last successful transfer finished. Select the destination to see its details and **transfer history**: one row per delivery, with the date, rows and volume sent, and a status.

![The Destinations table on the Data Share page](/_fern-files/_img/84c1aeefb5220513ba44fb0f707221174e55dd4e836c1457e2a8f975fed5370d.webp)

| Status                                                    | What it means                                                                                                               |
| --------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------- |
| **Success**                                               | The delivery finished.                                                                                                      |
| **Pending**, **Running**                                  | The delivery is queued or in progress.                                                                                      |
| **Error**, **Partial Failure**, **Expired**, **Orphaned** | The delivery didn't finish. Nothing is lost: the next delivery sends everything that changed since the last successful one. |
| **Cancelled**                                             | The delivery was stopped before it finished.                                                                                |

## Change or remove your destination

* **To update the connection details**, such as after rotating a password, select the destination, then **Edit**. Use **Test connection** before you select **Save changes**.
* **To remove the destination**, select it, then **Delete**. Deliveries stop, and this can't be undone. The tables already in your destination stay in place with the data they have, but they no longer update.
* **To move to a different warehouse**, delete the current destination and create the new one. Its first delivery sends all of your data.

## Troubleshooting

| Situation                                 | What to do                                                                                                                                                                                                             |
| ----------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Test connection** fails                 | Check the host, database, schema and credentials against your setup guide. Make sure Candid's user or role can create tables in the schema, and that [Candid's IP addresses](#allow-candids-ip-addresses) are allowed. |
| A delivery shows **Error**                | Check whether anything changed on your side, such as an expired password, a dropped schema or revoked permissions. Fix it with **Edit**, and the next nightly delivery catches up.                                     |
| **Create** is grayed out                  | Your organization already has a destination. Edit or delete it, or contact Candid if you need another.                                                                                                                 |
| The page says Data Share isn't configured | Data Share isn't turned on for your organization yet. Email [support@joincandidhealth.com](mailto:support@joincandidhealth.com).                                                                                       |
| Data looks stale or incomplete            | Check **Last transfer** and **transfer history**, then email [support@joincandidhealth.com](mailto:support@joincandidhealth.com) with the table name and an example ID.                                                |

## Supported destinations

Each setup guide lists what to create and grant on your side. The guides are maintained by Candid's data delivery partner and open on their site. As you follow one:

* **Use Candid's IP addresses.** Where a guide lists IP addresses to allowlist, use [Candid's](#allow-candids-ip-addresses) instead.
* **Find provided values in the form.** Anything a guide says is provided to you, such as a public key, a service account or a trust policy, is shown in the **Add destination** form in Candid.

### Warehouses

#### [Snowflake](https://docs.prequel.co/export/destinations/snowflake)

#### [BigQuery](https://docs.prequel.co/export/destinations/bigquery)

#### [Databricks](https://docs.prequel.co/export/destinations/databricks)

#### [Amazon Redshift](https://docs.prequel.co/export/destinations/redshift)

#### [Redshift Serverless](https://docs.prequel.co/export/destinations/redshift-serverless)

#### [Amazon Athena](https://docs.prequel.co/export/destinations/athena)

#### [ClickHouse](https://docs.prequel.co/export/destinations/clickhouse)

#### [MotherDuck](https://docs.prequel.co/export/destinations/motherduck)

### Databases

#### [Postgres](https://docs.prequel.co/export/destinations/postgres)

#### [Aurora / RDS Postgres](https://docs.prequel.co/export/destinations/aurora-postgres)

#### [MySQL](https://docs.prequel.co/export/destinations/mysql)

#### [Aurora MySQL](https://docs.prequel.co/export/destinations/aurora-mysql)

#### [SQL Server](https://docs.prequel.co/export/destinations/sql-server)

#### [Oracle](https://docs.prequel.co/export/destinations/oracle)

#### [MongoDB](https://docs.prequel.co/export/destinations/mongodb)

### Lakehouse tables

#### [Delta Lake](https://docs.prequel.co/export/destinations/delta-lake)

#### [Apache Iceberg](https://docs.prequel.co/export/destinations/iceberg)

Don't see your destination, or not sure which to pick? Email [support@joincandidhealth.com](mailto:support@joincandidhealth.com).