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

# Reply to a change request

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

## Request

- Base URL: `https://apihub.co.il`
- URL: `https://apihub.co.il/v1/messaging/sms/registrations/{id}/respond`
- Auth: HTTP bearer

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. When the request
was written as points (`reviewRequest` on the registration), send one
entry in `answers` per point. The registration
returns to `requested` (back in review), and you do not need to resubmit the
whole registration. A `rejected` registration can also be answered when
we asked for changes to fix it (`reviewRequest` set); it stays `rejected`. To change the submitted brand/campaign fields
themselves, resubmit via `POST /v1/sms/registrations` with
`resubmitRequestId` instead.


**Billing:** Request; paid actions are priced in credits (see GET /v1/messaging/prices) · **Rate limit:** 60/min

## Path parameters

- `id` string, required

## Headers

- `Idempotency-Key` string
- `X-Tag` string

## 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.
  - `answers` object[]: One answer per point of the open `reviewRequest`, each point at most once. Required (every point) when the request has points; a missing, repeated or unknown point is a 400 naming the point ids. At most 10 files per reply.
    - `url` string, uri: For `link` and `link_or_file` points.
    - `text` string: For `text` points (at least 3 characters).
    - `files` string[]: Hosted document URLs from POST /v1/sms/opt-in-proof, for `file` and `link_or_file` points.
    - `pointId` string, required
  - `requestId` string: The `reviewRequest.id` you are answering. When it no longer matches the open request the reply is refused with 409.

## Response `200`

Completed

- object
  - `id` string: Execution id — stable across internal retries; use it with GET /v1/executions/{id}
  - `status` 'pending' | 'processing' | 'completed' | 'partial' | 'failed' | 'cancelled' | 'timeout'
  - `operation` string
  - `tag` string, nullable: Your X-Tag, if sent
  - `created_at` string, date-time
  - `completed_at` string, date-time, nullable
  - `output` object: Operation result (see each operation). While a Studio render is processing: `stage` (queued · transcribing · downloading · preparing · cleaning_voice · mixing_audio · rendering · finishing), `phase` (the engine's: download · prepare · voice · audio · encode · qa · upload, or null), `progress` (a percent, 0–100) and `progress_fraction` (0–1), `eta_seconds` (seconds left, never below 0) and `estimate_seconds`
    - `status` 'requested' | 'rejected': requested = back in our review; rejected = a registration the carriers rejected, where we asked for these answers to fix it (it stays rejected while we do).
  - `error` string, nullable
  - `usage` object
    - `credits_charged` number, nullable
    - `credits_reserved` number
    - `estimated_credits` number
    - `cost_source` 'provider_reported' | 'calculated' | 'estimated' | 'null', nullable
    - `provider_usage` object, nullable: Normalised consumption, e.g. { VIDEO_SECOND: 22.4 }
  - `balance` object
    - `available` number
    - `reserved` number

## Other responses

- `400`: Invalid input
- `402`: Insufficient credits / project budget
- `404`: Resource not found (or not yours)
- `429`: Rate limited
- `503`: Service temporarily paused

---

[API](https://skmtc.dev/apihub/apis/apihub-one-api-for-chat-image-video-ai.md) · [All operations](https://skmtc.dev/apihub/apis/apihub-one-api-for-chat-image-video-ai/llms.txt) · [OpenAPI document](https://skmtc.dev/apihub/apis/apihub-one-api-for-chat-image-video-ai/revisions/a8caa42835ce?raw)