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

# Deeplinking

> Pre-fill account information in Bridge Widget flows to skip search steps

Pre-fill employer or provider information when creating a bridge token to bypass the search screens. Use this for DDS and PLL flows where you already know the user's employer or provider.

<Note>
  For Embedded Orders deeplinking (VOIE, VOE, VOA), see [Deeplinking for Embedded Orders](/developers/integration/embedded-orders/deeplinking).
</Note>

```mermaid theme={null}
sequenceDiagram
    participant Server as Your Server
    participant API as Truv API
    participant Bridge as Truv Bridge

    Server->>API: Search company mapping
    API-->>Server: company_mapping_id
    Server->>API: Create bridge token with company_mapping_id
    API-->>Server: bridge_token
    Note over Bridge: User skips search screens
    Bridge->>Bridge: User lands on login page
```

***

## Deeplink by employer

Use this when you know the user's employer name. Truv maps the employer to the correct payroll provider automatically.

### Find the company mapping

```bash theme={null}
curl --request GET \
     --url 'https://prod.truv.com/v1/company-mappings-search/?query=Facebook' \
     --header 'X-Access-Client-Id: YOUR_TRUV_CLIENT_ID' \
     --header 'X-Access-Secret: YOUR_TRUV_CLIENT_SECRET'
```

```json theme={null}
[
  {
    "company_mapping_id": "48427a36d43c4d5aa6324bc06c692456",
    "name": "Facebook",
    // ...
  }
]
```

### Create a bridge token with the mapping

Pass the `company_mapping_id` when creating the bridge token.

```bash theme={null}
curl --request POST \
     --url https://prod.truv.com/v1/users/USER_ID/tokens/ \
     --header 'X-Access-Client-Id: YOUR_TRUV_CLIENT_ID' \
     --header 'X-Access-Secret: YOUR_TRUV_CLIENT_SECRET' \
     --header 'Content-Type: application/json' \
     --data '{
  "product_type": "deposit_switch",
  "company_mapping_id": "48427a36d43c4d5aa6324bc06c692456"
}'
```

The user skips the employer search screen and lands directly on the provider login page.

***

## Deeplink by provider

Use this when you know the specific payroll provider (e.g. ADP, Workday, Gusto) but not the specific employer.

```bash theme={null}
curl --request POST \
     --url https://prod.truv.com/v1/bridge-tokens/ \
     --header 'X-Access-Client-Id: YOUR_TRUV_CLIENT_ID' \
     --header 'X-Access-Secret: YOUR_TRUV_CLIENT_SECRET' \
     --header 'Content-Type: application/json' \
     --data '{
  "product_type": "deposit_switch",
  "provider_id": "adp",
  "user": {
    "id": "99dd17074ac94aa9ace2621d657c7610"
  }
}'
```

<Note>
  All providers from the [List all data providers endpoint](/api-reference/data-providers/providers-list) are supported as deeplink targets.
</Note>

***

## Next steps

<CardGroup cols={2}>
  <Card title="Search Companies" icon="magnifying-glass" href="/api-reference/companies/company_mapping">
    Find `company_mapping_id` by employer name
  </Card>

  <Card title="List Providers" icon="list" href="/api-reference/data-providers/providers-list">
    All supported `provider_id` values
  </Card>

  <Card title="Bridge Token API" icon="key" href="/api-reference/bridge-token/users_tokens">
    Create bridge tokens with deeplink parameters
  </Card>

  <Card title="Embedded Orders Deeplinking" icon="code" href="/developers/integration/embedded-orders/deeplinking">
    Deeplinking for VOIE, VOE, and VOA flows
  </Card>
</CardGroup>