Sign in
Webhook Events

RCS agent status updated event

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.

postWebhookrcs.agent.status_updated

Payload

idstring

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'
timestampstring 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.

status'changes_requested' | 'brand_vetting' | 'agent_review' | 'testing' | 'launch_review' | 'launching' | 'live' | 'rejected' | 'deactivated'
reasonstring

Our review note on changes_requested, the reason on rejected, or why a launch filing bounced back to testing.

Response

Webhook received successfully

Changes

Webhooks have no change history: a webhook is keyed by its event name rather than a path and method, so no recorded change can name it.