Respond to the regulatory reviewer (message + corrections)
Send a single response to the reviewer on a number awaiting remediation:
a free-text message and/or corrected requirement documents, in one call.
If corrections are present they are PATCHed onto the requirement group and
re-submitted (the number goes back to "in review"); if a message or file
attachments are present they are posted to the reviewer's comment thread.
When both are present, your message is the thread comment and the resubmit
drives the state change. At least one of message, corrections, or
attachments is required. documents correct requirement slots; attachments
are loose files (their links are added to your message).
API key authentication - use your Zernio API key as a Bearer token
In: header
Path Parameters
Your message to the reviewer.
length <= 2000Corrected requirement documents, each keyed to its requirement.
A corrected address record, keyed to its requirement.
"individual" | "business" | nullLoose files (PDF/JPG/PNG/WEBP, max 10 MB each) whose links are added to your message.
items <= 5Response Body
application/json
application/json
application/json
import Zernio from '@zernio/node';const zernio = new Zernio({ apiKey: process.env.ZERNIO_API_KEY });const { data } = await zernio.phonenumbers.respondToPhoneNumberReviewer({ path: { id: 'abc123', }, body: { message: 'Hello, world!', documents: [ { requirementId: 'requirement_abc123', }, ], address: {}, },});console.log(data);{
"status": "resubmitted",
"posted": true,
"phoneNumber": {
"id": "string",
"status": "string"
},
"siblingsResubmitted": 0
}{
"error": "string",
"type": "invalid_request_error",
"code": "string",
"param": "string",
"platform": "string",
"platformError": {},
"details": {}
}{
"error": "Unauthorized"
}Reply to the regulatory reviewer POST
Post a free-text reply (with optional file attachments) to the reviewer on a number awaiting remediation — for asks the structured form can't express (e.g. "is this personal or business?"). Attachments are stored by us and their links are added to the reviewer's comment thread (the carrier's number order takes no loose files). A reply to a comment-style ask moves the number back to "in review"; a reply on a formal decline is supplementary and you must still resubmit the fix. Requires text or at least one attachment.
Pre-review a KYC packet POST
Advisory dry-run of a regulated-KYC packet before submitting: reviews the exact documents the regulator will see (referenced by the ids from POST /v1/phone-numbers/kyc/upload-document) against the declared values and address, and returns plain-language advisories for likely decline reasons (wrong document type, mismatched address, one-sided ID scans). Non-blocking: advisories are warnings, submitting anyway is always allowed, and any review failure degrades to an empty list.