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

# Connections

> A connection is one credential presented through one provider. You activate it, enable it in a workflow, and verify with it.

A **connection** is one way to verify an identity: a **credential** (what is proven, such as a US mobile driver's license) presented through a **provider** (where it lives, such as Google Wallet).

```mermaid theme={null}
flowchart LR
  P1[Google Wallet] --> C1[US mDL]
  P2[Samsung Wallet] --> C1
  P3[CA DMV Wallet] --> C1
  P1 --> C2[US passport]
  P4[Smart-ID] --> C3[Smart-ID]
  classDef cred fill:#DBEAFE,stroke:#2563EB,color:#111;
  classDef prov fill:#ECECEC,stroke:#222,color:#111;
  class C1,C2,C3 cred
  class P1,P2,P3,P4 prov
```

Each arrow above is one connection, for example `google-wallet-us-mdl` or `smart-id`. The same credential through three providers is three connections, because each provider has its own activation and availability.

## Using a connection

1. **Activate** it for your app. See [Activate Connections](/v2/guides/concepts/connections/activation).
2. **Enable** it in a workflow. See [Workflows](/v2/guides/verifications/workflows).
3. **Verify** with it over OIDC or REST.

## Identifiers

| Identifier | Example | Use it for |
| :- | :- | :- |
| **Connection ID** | `smart-id` | The id you send: `connectionId` (REST) or `ui_connection_id` (OIDC). From the catalog, the same for every app. |
| **Connection instance ID** | `conn_01J8XK2P4M9QR3TV` | Created when you activate a connection for one app. Send it as `connectionInstanceId` (REST) or `ui_connection_instance_id` (OIDC). |
| **Provider ID / Credential ID** | `google-wallet` / `us-mdl` | Filtering and display. |

<Warning>
  A connection ID is readable but opaque. Do not parse it. Read `provider.id` and `credential.id` from [Get Connections](/v2/api-reference/verifications/get-connections).
</Warning>

## What a connection tells you

[Get Connections](/v2/api-reference/verifications/get-connections) and the connection's detail sheet in the Console show:

* **Countries** and the **display name** users see
* **Flow type**: how the user completes it. See [Verification Flow](/v2/guides/verifications/verification-flow#flow-types)
* **Verification model**: `disclosure` or `match`. See [Verification Model](/v2/guides/concepts/verification-model)
* **Level of assurance** it can reach. See [Assurance](/v2/guides/verifications/assurance)
* **Available claims**, and the **user input** it needs. See [User Input](/v2/api-reference/verifications/user-input)

The Console also shows whether a connection is available in Sandbox, Production, or both.

<Tip>
  For how credentials and providers relate in depth, see [Credentials & Providers](/v2/guides/concepts/connections/providers-and-credentials).
</Tip>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.