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.whatsappphonenumbers.remediateWhatsAppNumber({ 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"
}Get declined requirements GET
For a number in `regulatory_declined`, returns ONLY the requirements the reviewer flagged declined, as a form spec (same shape as the KYC form GET). The customer fixes just those — Telnyx supports correcting a declined requirement group and re-submitting it (no new number/group). Falls back to the full spec if the provider exposes no per-requirement flags.
List flows GET
List all WhatsApp Flows for the Business Account (WABA) associated with the given account.