Webhook Events

RCS agent status updated event

An RCS agent moved into a new customer-visible status; status is the new one.

Statuses

changes_requested (note in reason), brand_vetting, agent_review, testing, launch_review, launching, live, rejected (reason says why), deactivated. In testing, add test phones, then file the launch; a reason means it bounced.

When it fires

Fires once per move into a status. requested sends nothing. Overlapping status checks never send the same status twice in a row.

Payload notes

agent.profileId is the owning profile. agent.accountId is null when the agent has no linked account.

postWebhookrcs.agent.status_updated

Payload

testboolean

Always true when present: only a sample sent by POST /v1/webhooks/test with an event carries it. Real deliveries never do.

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.

Example payload

{
  "profiles": [
    {
      "externalId": "tenant_42"
    }
  ]
}

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.