---
title: "SMS registration action required event"
method: POST
path: "sms.registration.action_required"
tags: ["Webhook Events"]
---

# SMS registration action required event

`POST sms.registration.action_required` (webhook)

Fired when an SMS registration starts waiting on its owner. `reason` says why:
`changes_requested` (we need answers to some points, before submission or to fix a
carrier rejection; `message` is the request, answer with
POST /v1/sms/registrations/{id}/respond), `otp_required` (a sole-proprietor brand needs
the code texted to its mobile, submit it with POST /v1/sms/registrations/{id}/verify-otp)
or `carrier_info_required` (the toll-free carrier asked for more information; the request
expires after 7 days). A carrier rejection alone does not fire it: we handle the fix, see
`sms.registration.status_updated`. Fires once per new request (not on follow-up messages)
and once per OTP or carrier request.

## Payload

- object
  - `id` string
  - `event` 'sms.registration.action_required'
  - `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.
  - `registration` object
    - `id` string
    - `type` 'standard_10dlc' | 'sole_prop_10dlc' | 'toll_free'
    - `displayName` string, nullable
    - `status` string — Registration status when the event fired (changes_requested, pending or rejected).
    - `profileId` string
  - `reason` 'changes_requested' | 'otp_required' | 'carrier_info_required'
  - `message` string — What to do, in words: our request or the carrier's note. Absent for otp_required.

## 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/b2325332041a?raw)