---
title: "Escalation Reachability"
method: POST
path: "/internal/notifications/escalation-reachability"
---

# Escalation Reachability

`POST /internal/notifications/escalation-reachability`

## Request

- Base URL: `https://api-docs.upsmith.com` (the document declares no server; this is the origin it was published from)
- URL: `https://api-docs.upsmith.com/internal/notifications/escalation-reachability`
- Auth: API key in header `x-api-key`

## Headers

- `organization-id` string, nullable
- `timezone` string
- `x-user-id` string, nullable
- `x-actor-email` string, nullable
- `x-request-source` string, nullable
- `x-operation-id` string, nullable
- `x-commit-message` string, nullable
- `x-confirmation-id` string, nullable
- `x-chat-id` string, nullable

## Request body

- EscalationReachabilityRequest
  - `organization_id` string, required
  - `agent_v2_ids` string[]
  - `roster_ids` string[]
  - `check_recipients` boolean

## Response `200`

Successful Response

- EscalationReachability
  - `module_active` boolean, required
  - `subscribed_count` integer
  - `reachable_count` integer
  - `reason_counts` object
  - `source` 'subscriptions' | 'rules': Which configuration the counts were read from. Only the rules route an escalation, so only ``RULES`` is produced; the field is still served for a caller deployed before that was true.
  - `rule_count` integer
  - `invalid_rule_count` integer
  - `rotation_count` integer
  - `empty_rotation_ids` string[]

## Other responses

- `422`: Validation Error

---

[API](https://skmtc.dev/upsmith/apis/upsmith-api.md) - [All operations](https://skmtc.dev/upsmith/apis/upsmith-api/llms.txt) - [OpenAPI document](https://skmtc.dev/upsmith/apis/upsmith-api/revisions/86e2c2bd93af?raw)