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

# Tracking Dependencies

> Track third-party service health as dependencies with DevHelm Status Data

By the end of this guide, you'll have services from the Status Data catalog added as dependencies, with alerts configured to notify you when they have outages.

<Accordion title="Prerequisites">
  * DevHelm CLI installed or an API token
  * At least one alert channel — see [First alert](/guides/first-alert)
</Accordion>

For conceptual background, see [Dependencies](/status-data/dependencies).

## Add your first dependency

<Steps>
  <Step title="Browse the catalog">
    <CodeGroup>
      ```bash CLI theme={null}
      devhelm services list
      devhelm services list --search stripe
      devhelm services list --category cloud-infrastructure
      ```

      ```bash API theme={null}
      curl "https://api.devhelm.io/api/v1/services?limit=20"
      curl "https://api.devhelm.io/api/v1/services?search=stripe"
      ```
    </CodeGroup>

    Find the services your application depends on — GitHub, Stripe, AWS, Vercel, etc.
  </Step>

  <Step title="Add a dependency">
    <CodeGroup>
      ```bash CLI theme={null}
      devhelm dependencies track github
      devhelm dependencies track stripe
      devhelm dependencies track aws
      ```

      ```bash API theme={null}
      curl -X POST https://api.devhelm.io/api/v1/service-subscriptions/github \
        -H "Authorization: Bearer $DEVHELM_API_TOKEN"

      curl -X POST https://api.devhelm.io/api/v1/service-subscriptions/stripe \
        -H "Authorization: Bearer $DEVHELM_API_TOKEN"
      ```
    </CodeGroup>
  </Step>

  <Step title="Configure alert sensitivity">
    Control which events trigger alerts:

    ```bash theme={null}
    devhelm dependencies update <subscription-id> \
      --alert-sensitivity INCIDENTS_ONLY
    ```

    New dependencies start in `AWARENESS` (silent tracking — the incident is recorded on the dashboard but no alert channels fire). Switch to one of the paging modes when you're ready to be alerted:

    | Level            | Behavior                                                                   |
    | ---------------- | -------------------------------------------------------------------------- |
    | `AWARENESS`      | **Default.** Tracks real vendor incidents on the dashboard but never pages |
    | `INCIDENTS_ONLY` | Pages on real vendor incidents (any severity)                              |
    | `ALL`            | Pages on any status change, including synthetic degradations               |
    | `MAJOR_ONLY`     | Pages only on major outages                                                |
  </Step>

  <Step title="Verify routing">
    Dependency alerts route through the same notification policies as monitor alerts. Verify with a catch-all policy or create a targeted one:

    ```json theme={null}
    {
      "name": "Dependency alerts to Slack",
      "matchRules": [
        { "type": "service_id_in", "values": ["<github-service-id>", "<stripe-service-id>"] }
      ],
      "escalation": {
        "steps": [{
          "delayMinutes": 0,
          "channelIds": ["<slack-channel-id>"]
        }]
      }
    }
    ```
  </Step>
</Steps>

## Track specific components

If you only depend on part of a service (e.g., GitHub API but not GitHub Pages), add a component-level dependency:

<CodeGroup>
  ```bash CLI theme={null}
  devhelm dependencies track github --component <component-id>
  ```

  ```bash API theme={null}
  curl -X POST "https://api.devhelm.io/api/v1/service-subscriptions/github" \
    -H "Authorization: Bearer $DEVHELM_API_TOKEN" \
    -H "Content-Type: application/json" \
    -d '{ "componentId": "<component-id>" }'
  ```
</CodeGroup>

Find component IDs by listing a service's components:

```bash theme={null}
devhelm services components github
```

## Manage dependencies

```bash theme={null}
devhelm dependencies list
devhelm dependencies delete <subscription-id>
```

<Note>
  Free plans support up to 10 dependencies. Starter and above have unlimited.
</Note>

## Next steps

<CardGroup cols={2}>
  <Card title="Dependencies reference" icon="link" href="/status-data/dependencies">
    Alert sensitivity, component tracking, and plan limits.
  </Card>

  <Card title="Service incidents" icon="circle-exclamation" href="/status-data/incidents">
    View incidents from your tracked services.
  </Card>

  <Card title="Uptime reporting" icon="chart-bar" href="/guides/uptime-reporting">
    Query historical uptime for your dependencies.
  </Card>
</CardGroup>