---
title: "Reply to a change request"
method: POST
path: "/v1/sms/registrations/{id}/respond"
tags: ["SMS"]
---

# Reply to a change request

`POST /v1/sms/registrations/{id}/respond`

Replies to a reviewer change request on a registration in
`changes_requested` state: a note, hosted document URLs (from
`POST /v1/sms/opt-in-proof`), or both, sent together. The registration
returns to `requested` (back in review) — no need to resubmit the
whole registration. To change the submitted brand/campaign fields
themselves, resubmit via `POST /v1/sms/registrations` with
`resubmitRequestId` instead.

## Path parameters

- `id` string, required

## Request body

- object
  - `note` string — Answer for the reviewer. Required when no files are sent.
  - `files` string[] — Hosted document URLs returned by POST /v1/sms/opt-in-proof.

## Response `200`

Reply recorded; the registration is back in review.

- object
  - `status` 'requested'

## Other responses

- `400` — Invalid request
- `401` — Unauthorized
- `404` — Registration not found
- `409` — Registration is not waiting on changes

---

[API](https://skmtc.net/zernio/apis/zernio-api.md) · [All operations](https://skmtc.net/zernio/apis/zernio-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/zernio/zernio-api/versions/51932b099b2f/schema)