---
title: "Get the status of a broadcast"
method: GET
path: "/v1/campaigns/{broadcast_id}/triggers/{trigger_id}"
tags: ["Broadcasts"]
---

# Get the status of a broadcast

`GET /v1/campaigns/{broadcast_id}/triggers/{trigger_id}`

## Request

- Base URL: `https://api.customer.io`
- URL: `https://api.customer.io/v1/campaigns/{broadcast_id}/triggers/{trigger_id}`
- Auth: HTTP bearer

After triggering a broadcast you can retrieve the status of that broadcast using a GET of the `trigger_id`. You can retrieve the `trigger_id` from [Get broadcast triggers](/integrations/api/app/tag/broadcasts/listBroadcastTriggers/).

## Response `200`

Returns the status of your broadcast.

- object
  - `trigger` BroadcastTriggerObject: You can get triggers to know when you triggered a broadcast and whether or not it's been processed.
    - `id` integer: The identifier for a broadcast trigger.
    - `broadcast_id` integer: The identifier for a broadcast.
    - `created_at` integer: The date time when the referenced ID was created.
    - `processed_at` integer: The date-time when Customer.io processed the trigger.
    - `scheduled_at` integer: The date-time this trigger is scheduled to send at, or `0` if you didn't schedule it.
    - `cancelled_at` integer: The date-time you canceled this trigger, or `0` if you haven't canceled it.
    - `expires_after` integer: The send window in seconds that you set when you triggered the broadcast, or `0` if the send has no expiry.
    - `rate_limit` object: The rate limit you set when you triggered the broadcast. We omit this field if you didn't set one.
      - `rate` integer: The maximum number of people that enter the broadcast in each `period`.
      - `period` 'minute' | 'hour' | 'day': The length of each period.
      - `spread` boolean: Whether we let people in at an even pace across the period.
    - `audience_count` integer: The number of people in the trigger's audience. For a send without a `rate_limit`, we set it when the send finishes. For a rate-limited send, we set it when the first people enter. It is `0` until then.

## Other responses

- `400`: The `broadcastID`, `actionID` or `triggerID` is invalid.
- `404`: The broadcast, action, and/or trigger do not exist.
- `429`: Your request is over the 10-per-second limit. `Retry-After` tells you how many seconds you must wait before you send the next request.

## Changes

- **2026-10-17** `2415f42044d0`: 7 warning, 1 info
  - removed the optional property `broadcast_id` from the response with the `200` status
  - removed the optional property `cancelled_at` from the response with the `200` status
  - removed the optional property `created_at` from the response with the `200` status
  - removed the optional property `expires_after` from the response with the `200` status
  - …4 more
- **2026-09-23** `ba583d6489da`: 3 info
  - added the optional property `cancelled_at` to the response with the `200` status
  - added the optional property `expires_after` to the response with the `200` status
  - added the optional property `scheduled_at` to the response with the `200` status
- **2026-09-02** `5da2740beeb5`: 1 info
  - added the media type `application/json` for the response with the status `429`

[Operation history](https://skmtc.dev/customer/apis/customer-io-journeys-api-reference/changes/v1/campaigns/:broadcast_id/triggers/:trigger_id/get.md)

---

[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.dev/customer/apis/customer-io-journeys-api-reference/revisions/ac0b282053fe?raw)