# ChannelDock setup: create API keys and connect with Support

ChannelDock connects with an API key and API secret. Create separate credentials for Optiply, then coordinate the connection with Optiply Support.

## Before you connect ChannelDock

Open the intended ChannelDock account and the matching Optiply account. Ask your ChannelDock administrator for access if you cannot manage API keys.

Agree the data flows and stock locations with Support before connection. The [ChannelDock mapping guide](/article/integrations-data-mappings-public-channeldock) explains the incoming fields and optional stock rules.

Keep keys private. Enter them only in the connection form or the secure setup route agreed with Support.

## Steps to connect ChannelDock

### Create ChannelDock credentials

1. Sign in to the intended ChannelDock account.
2. Open **Settings → API & Webhooks**.
3. Under **API keys**, select **Generate new API keys**.
4. Give the credentials a clear description, such as Optiply.
5. Store the API key and API secret securely.
6. Ask Support to confirm the endpoint permissions needed for your agreed flows.

ChannelDock recommends separate credentials for each integration and limited endpoint permissions. See the [official ChannelDock API setup instructions](https://channeldock.com/help/en/integrations-api/api/channeldock-rest-api-documentation/).

### Prepare the Optiply connection

1. In Optiply, open **Settings → Integrations**.
2. Wait for the source lists to load.
3. Select **Add a source**.
4. Search for ChannelDock under **WMS & Fulfilment** in **Select a source**.
5. Select **Channeldock** and choose **Next** to open **Connect to system**.
6. Enter the key in **Your API Key** and the secret in **Your API Secret**.
7. Contact Support before submitting the connection details.

If **Contact us** is offered, use that control. Otherwise, use [Optiply Support](/support).

![ChannelDock source selection.](/screenshots/channeldock/select-source.webp)

![ChannelDock API key and API secret fields with no credentials entered.](/screenshots/channeldock/connection-fields.webp)

Tell Support the intended account, required flows, stock locations and the step you reached. Do not include keys or secrets in messages or screenshots.

### Check the linked ChannelDock source

1. After setup, return to **Settings → Integrations**.
2. Check the intended source for the **Connected** label.
3. Compare an agreed product or order in both systems.

## Fields in the ChannelDock connection form

| Field or control | What you use it for |
| --- | --- |
| **Your API Key** | The key created for this integration |
| **Your API Secret** | The matching secret, not another key |
| **Contact us** | Setup assistance when offered |
| **Connected** | A linked source, separate from record transfer |

## What you see when ChannelDock setup worked

The intended source appears as **Connected** after setup succeeds. Your agreed record checks confirm data arrival separately.

## Limits of ChannelDock setup

Connector availability can differ by account. ChannelDock applies API limits per key. Support must check connection timing and required permissions for your account.

The additional outbound-delivery import option still sends data from ChannelDock to Optiply. It is not an Optiply-to-ChannelDock order export.

## If ChannelDock setup did not work

- **Add a source** disabled: wait for the lists to load, then contact Support if it remains disabled.
- Connector missing: contact Support instead of selecting another connector.
- Key creation unavailable: ask your ChannelDock administrator for help.
- Credentials rejected: check the key-secret pair and intended account through the secure setup route.
- Rate-limit error: ask Support to check the limit and connection timing before another attempt.
- Source missing or data absent: ask Support to check linking and record transfer separately.

## Related articles on ChannelDock and integrations

- [ChannelDock data mapping](/article/integrations-data-mappings-public-channeldock)
- [Custom and partner integrations](/article/custom-and-partner-integrations)
