---
title: "Get a live notification's status"
method: GET
path: "/v1/live_notifications/{instance_id}"
tags: ["Live Notifications"]
---

# Get a live notification's status

`GET /v1/live_notifications/{instance_id}`

Look up a live notification's current state, lifecycle timestamps, and the status of its most recent delivery.

## Path parameters

- `instance_id` string, required

## Response `200`

The activity's current status.

- object
  - `instance_id` string — The activity's instance ID.
  - `notification_type` string — The activity's reverse-DNS type identifier.
  - `platform` string — The device platform—`ios` or `android`.
  - `state` 'active' | 'ended' | 'expired' | 'failed' — The activity's lifecycle state.
  - `failure_reason` string, nullable — Why the activity failed, when `state` is `failed`.
  - `started_at` integer — When the activity started (unix timestamp).
  - `ended_at` integer, nullable — When the activity ended (unix timestamp).
  - `expires_at` integer, nullable — When the activity expires (unix timestamp).
  - `last_delivery` object, nullable — The most recent delivery for the activity.
    - `id` string — The delivery ID.
    - `operation` 'start' | 'update' | 'end' — The lifecycle operation the delivery carried.
    - `status` 'queued' | 'sent' | 'failed' | 'undeliverable' — The delivery's status.
    - `source` string — Where the operation originated—the API or the device.
    - `created_at` integer — When the delivery was created (unix timestamp).

## Other responses

- `400` — `instance_id` isn't a valid ULID.
- `404` — The activity wasn't found—a recently started one may not be processed yet—or live notifications aren't enabled for this workspace.

---

[API](https://skmtc.dev/customer/apis/customer-io-journeys-api-reference.md) · [All operations](https://skmtc.dev/customer/apis/customer-io-journeys-api-reference/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/customer/customer-io-journeys-api-reference/revisions/4b391af7cb06/schema)