---
title: "RCS agent status updated event"
method: POST
path: "rcs.agent.status_updated"
tags: ["Webhook Events"]
---

# RCS agent status updated event

`POST rcs.agent.status_updated` (webhook)

Fired on every customer-visible status change of an RCS agent: `changes_requested`
(we need changes before filing, `reason` is our note), `brand_vetting`, `agent_review`,
`testing` (add test phones, then send the launch filing; with a `reason` the launch
filing bounced), `launch_review`, `launching`, `live` (the agent can message any
RCS-capable phone), `rejected` (`reason` says why) and `deactivated`.

## Payload

- object
  - `id` string — Stable webhook event ID: the dedupe key, also sent as the X-Zernio-Event-Id header and identical on every retry and redelivery. It identifies the event only, never an account or other resource.
  - `event` 'rcs.agent.status_updated'
  - `timestamp` string, date-time — UTC time at which Zernio generated this event (set once when the event payload is built, before delivery is queued). Retries and redeliveries keep the original value, so it reflects the event, not the delivery attempt.
  - `agent` object
    - `id` string
    - `displayName` string
    - `profileId` string
    - `accountId` string, nullable — The rcs inbox account, once the agent exists with the carriers.
  - `status` 'changes_requested' | 'brand_vetting' | 'agent_review' | 'testing' | 'launch_review' | 'launching' | 'live' | 'rejected' | 'deactivated'
  - `reason` string — Our review note on changes_requested, the reason on rejected, or why a launch filing bounced back to testing.

## Acknowledgement `200`

Webhook received successfully

---

[API](https://skmtc.dev/zernio/apis/zernio-api.md) · [All operations](https://skmtc.dev/zernio/apis/zernio-api/llms.txt) · [OpenAPI document](https://skmtc.dev/zernio/apis/zernio-api/revisions/16a7b9d5373e?raw)