SMS

Reply to a change request

Changed on

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.

post/v1/sms/registrations/{id}/respond

Request

  • Base URL: https://zernio.com/api
  • URL: https://zernio.com/api/v1/sms/registrations/{id}/respond
  • Auth: HTTP bearer

Path parameters

idstring required

Request body

notestring

Answer for the reviewer. Required when no files are sent.

filesstring[]

Hosted document URLs returned by POST /v1/sms/opt-in-proof.

requestIdstring

The reviewRequest.id you are answering. When it no longer matches the open request the reply is refused with 409.

Response

Reply recorded; the registration is back in review.

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).

Changes

  • 450ec6ec5b0eRevision changes
    • info

      added the non-success response with the status

  • f8c8f34fb41aRevision changes
    • warning

      added the new account enum value to the / response property for the response status

    • warning

      added the new account enum value to the / response property for the response status