Resubmit a declined number
Submit corrected values/documents for the declined requirement(s). We
PATCH them onto the SAME requirement group and re-submit it for approval;
the number goes regulatory_declined → pending_regulatory. No new
number and no new billing. Body shape matches the KYC submit (values /
documents / address) — send only the corrected fields.
API key authentication - use your Zernio API key as a Bearer token
In: header
Path Parameters
Same shape as the KYC submit address.
Response Body
application/json
application/json
import Zernio from '@zernio/node';const zernio = new Zernio({ apiKey: process.env.ZERNIO_API_KEY });const { data } = await zernio.phonenumbers.remediatePhoneNumber({ path: { id: 'abc123', }, body: { values: {}, documents: [ { requirementId: 'requirement_abc123', filename: 'Example', base64: 'string', }, ], address: {}, },});console.log(data);{
"status": "resubmitted",
"phoneNumber": {
"id": "string",
"status": "string"
}
}{
"error": "Unauthorized"
}Release phone number DELETE
Release a purchased phone number. This will: 1. Disconnect any linked WhatsApp social account 2. Decrement the Stripe subscription quantity (or cancel if last number) 3. Release the number from Telnyx 4. Mark the number as released
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.