> ## Documentation Index
> Fetch the complete documentation index at: https://docs.zenoo.com/llms.txt
> Use this file to discover all available pages before exploring further.

# How Do I Connect Providers?

> Add verification providers to Zenoo Studio — enter credentials, configure settings, test connections, and enable them in your flows.

# How Do I Connect Providers?

Zenoo Studio acts as an orchestration layer that routes checks to external verification providers. Before you can use a provider in your flows, you need to connect it with API credentials and configure its settings.

## What you'll learn

* Which provider types are supported
* How to add a new provider
* How to configure timeout, retry, and batch settings
* How to test the connection
* How to enable a provider in your flows

## What providers does Zenoo support?

Zenoo supports providers across several verification categories:

| Category             | Providers                           | What they do                                               |
| -------------------- | ----------------------------------- | ---------------------------------------------------------- |
| **Screening**        | WorldCheck, ComplyAdvantage, Sumsub | PEP, sanctions, adverse media, and watchlist screening     |
| **Company Registry** | Kyckr                               | Company registration lookup, director/UBO extraction       |
| **Identity**         | Document verification providers     | ID document capture, OCR, authenticity checks              |
| **Biometric**        | Liveness detection providers        | Selfie matching, liveness verification, deepfake detection |
| **Address**          | Address verification providers      | Proof of address validation                                |

<Info>
  New providers can be added to the platform without code changes. Each provider is implemented as an adapter that follows a standard interface, making the system extensible.
</Info>

## How do I add a provider?

<Steps>
  <Step title="Navigate to Provider Settings">
    From the Studio dashboard, open **Settings** in the left navigation, then select **Providers**. You will see a list of configured providers and an **Add Provider** button.
  </Step>

  <Step title="Select the provider type">
    Click **Add Provider** and choose from the available provider catalog. Each entry shows:

    * Provider name and logo
    * Categories supported (screening, identity, company, etc.)
    * Whether it operates in individual or batch mode
  </Step>

  <Step title="Enter API credentials">
    Fill in the credentials for your provider account:

    * **API Key / API Secret** — provided by the vendor when you sign up
    * **Environment** — select Staging or Production (use staging for testing)
    * **Base URL** — pre-filled for known providers, editable for custom endpoints

    <Warning>
      Store production API credentials securely. Never share them in emails or chat. Zenoo encrypts credentials at rest using Named Credentials.
    </Warning>
  </Step>

  <Step title="Configure timeouts and retries">
    Set operational parameters for the provider:

    * **Timeout (seconds)** — how long to wait for a response before treating the call as failed (default: 30 seconds)
    * **Max retries** — how many times to retry on transient failures (default: 3)
    * **Retry delay** — seconds between retry attempts

    These settings prevent a single slow provider from blocking your entire verification flow.
  </Step>

  <Step title="Configure batch mode (if applicable)">
    Some providers support **batch mode**, where a single API call returns results for multiple check types. For example, WorldCheck returns PEP, Sanctions, and Adverse Media results in one call.

    If your provider supports batch mode:

    * Toggle **Category Batch Mode** on
    * Select which check types should be grouped in a single call
  </Step>

  <Step title="Test the connection">
    Click **Test Connection**. Studio sends a test request to the provider's API using your credentials and displays:

    * **Connection status** — success or failure
    * **Response time** — how long the test took
    * **Error details** — if the test failed, what went wrong (invalid credentials, network error, timeout)

    <Tip>
      Always test with staging credentials first. Switch to production credentials only when you are ready to go live.
    </Tip>
  </Step>

  <Step title="Enable the provider">
    Once the connection test passes, toggle the provider to **Active**. It will now appear as an option when configuring check nodes in the flow builder.
  </Step>
</Steps>

## How do I switch providers?

If you need to change a provider (e.g., migrating from one screening vendor to another):

1. Add and test the new provider using the steps above
2. Open your flow in the builder
3. Click each check node that uses the old provider
4. Change the **Provider** dropdown to the new provider
5. Save and test the flow
6. Deactivate the old provider once you confirm everything works

<Info>
  Check results from the old provider remain attached to their original cases. Switching providers only affects new flow executions.
</Info>

## What's next?

<Columns cols={2}>
  <Card title="Build Your First Flow" icon="play" href="/guides/studio/your-first-flow">
    Use your connected provider in a verification flow.
  </Card>

  <Card title="Screen for Sanctions" icon="shield-halved" href="/guides/studio/screen-for-sanctions">
    Configure screening nodes with your screening provider.
  </Card>

  <Card title="Go-Live Checklist" icon="clipboard-check" href="/guides/studio/go-live-checklist">
    Verify all providers are configured with production credentials before launch.
  </Card>

  <Card title="Brand Your Experience" icon="palette" href="/guides/studio/brand-your-experience">
    Customize the customer-facing verification journey.
  </Card>
</Columns>