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

# See who's on call from your own tools

> Answer "who is on call?" in your own tools, scripts, and AI assistants, without anyone opening the dashboard.

The dashboard and mobile app will always tell you who's on call, but sometimes you want that answer somewhere else: an internal portal, a chat bot, a script. You can get it from the [API](#with-the-api), the [CLI](#with-the-cli), or an [AI assistant](#with-an-ai-assistant). For Slack, your calendar, and incident roles we already keep things in sync for you, so skip to [Keep other tools in sync](#keep-other-tools-in-sync).

"Who's on call" can mean two different things, and they come from different endpoints:

* **Who gets paged for this service right now?** That's the escalation path's current responders. They follow the same rules as a real page, including working hours and levels, so this is the answer to "who do I call". See [What determines if you're on call?](https://docs.incident.io/on-call/determining-on-call.md)
* **Who is on this schedule?** That's the schedule's shifts, either right now or over any window of time.

## With the API

Use an [API key](https://docs.incident.io/admin/api-keys.md) with the **View on-call resources** permission.

### Who gets paged for an escalation path

[Escalation paths](https://docs.incident.io/api-reference/escalation-paths-v2/list.md) include `current_responders`: the people who would be paged first if the path fired right now.

```bash theme={null}
curl --get 'https://api.incident.io/v2/escalation_paths/<ESCALATION_PATH_ID>' \
  --header 'Authorization: Bearer <YOUR_API_KEY>'
```

### Who is on a schedule now, and next

[Schedules](https://docs.incident.io/api-reference/schedules-v2/list.md) include `current_shifts`, the shifts happening now, and `next_shifts`, who takes over at the next changeover.

```bash theme={null}
curl --get 'https://api.incident.io/v2/schedules/<SCHEDULE_ID>' \
  --header 'Authorization: Bearer <YOUR_API_KEY>'
```

### Who is on a schedule over a window of time

If you're building a calendar, looking up who was on call when something happened, or exporting upcoming shifts, list the [schedule entries](https://docs.incident.io/api-reference/schedule-entries-v2/list.md) for a window instead:

```bash theme={null}
curl --get 'https://api.incident.io/v2/schedule_entries' \
  --header 'Authorization: Bearer <YOUR_API_KEY>' \
  --data 'schedule_id=<SCHEDULE_ID>' \
  --data 'entry_window_start=2026-10-01T00:00:00Z' \
  --data 'entry_window_end=2026-10-08T00:00:00Z'
```

Use the `schedule_entries.final` list in the response. Overrides are already applied to it, so it matches what responders see in the dashboard.

## With the CLI

The [`inc` CLI](https://docs.incident.io/integrations/cli) can answer the same questions from your terminal, which is handy for scripts and cron jobs. Pass `--jq` to pick out just the names:

```bash theme={null}
# Who gets paged for an escalation path right now
inc escalations paths show <ESCALATION_PATH_ID> --jq '.current_responders | map(.name)'

# Who is on a schedule now, and next
inc schedules show <SCHEDULE_ID> --jq '{now: [.current_shifts[].user.name], next: [.next_shifts[].user.name]}'

# Who is on a schedule over a window of time
inc schedules entries <SCHEDULE_ID> --from 2026-10-01T00:00:00Z --until 2026-10-08T00:00:00Z
```

## With an AI assistant

Connect the [incident.io MCP server](https://docs.incident.io/ai/remote-mcp.md) to Claude, Cursor, or any other assistant that supports MCP, and just ask: "Who's on call for the platform team right now?"

## Keep other tools in sync

There are a few places we already push on-call information for you, so there's nothing to build:

* **Slack**: [sync a schedule to a Slack user group](https://docs.incident.io/on-call/sync-slack-groups.md), so `@platform-oncall` always reaches whoever is on call.
* **Your calendar**: [subscribe to your shifts](https://docs.incident.io/on-call/shift-calendar-feeds.md) as a calendar feed.
* **Incident roles**: [assign incident roles from a schedule](https://docs.incident.io/on-call/schedule-to-incident-roles.md), so whoever is on call becomes the incident lead automatically.
