---
title: "uptimeify_im_on_call"
description: "Who is on call right now (read at plan time, so it changes between runs). Incident Management must be active for the organization."
---

Who is on call right now (read at plan time, so it changes between runs). Incident Management must be active for the organization.

## Example Usage

```terraform
# Who holds the pager of team 7 right now, per escalation tier.
data "uptimeify_im_on_call" "platform" {
  team_id = 7
}

output "first_tier_on_call" {
  value = [for u in data.uptimeify_im_on_call.platform.tiers[0].users : u.user_name]
}
```

## Schema

### Optional

- `schedule_id` (Number) Only this schedule.
- `team_id` (Number) Only this team; also fills `tiers`.

### Read-Only

- `entries` (Attributes List) One entry per schedule with someone on call now (`GET /api/im/on-call`), after the filters. (see [below for nested schema](#nested-schema-for-entries))
- `tiers` (Attributes List) With `team_id`: one entry per escalation tier of the team with everyone on call now (`GET /api/im/teams/{id}/on-call-now`), overrides applied. Null without `team_id`. (see [below for nested schema](#nested-schema-for-tiers))

### Nested Schema for `entries`

Read-Only:

- `schedule_id` (Number)
- `shift_ends_at` (String) End of the current shift (RFC 3339).
- `team_id` (Number)
- `user_id` (String) User id.
- `user_image` (String) Avatar URL, may be null.
- `user_name` (String) Display name, may be null.


### Nested Schema for `tiers`

Read-Only:

- `tier_id` (Number)
- `tier_order` (Number)
- `uncovered_since` (String) Since when nobody covers the tier; null when covered or not within 14 days.
- `users` (Attributes List) (see [below for nested schema](#nested-schema-for-tiersusers))

### Nested Schema for `tiers.users`

Read-Only:

- `user_id` (String) User id.
- `user_image` (String) Avatar URL, may be null.
- `user_name` (String) Display name, may be null.