Get the declined requirements to fix
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.
API key authentication - use your Zernio API key as a Bearer token
In: header
Path Parameters
WhatsAppPhoneNumber id.
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.getWhatsAppNumberRemediation({ path: { id: 'abc123', },});console.log(data);{
"country": "string",
"numberType": "string",
"declineReason": "string",
"fields": [
{}
]
}{
"error": "Unauthorized"
}Get regulated-number KYC form spec GET
For a Tier 3/4 country, the fields the end customer must provide (Telnyx regulatory requirements) before a number can be ordered: text, date, address, or file (document) per requirement.
List offerable number countries GET
The WhatsApp number countries available to purchase, each with its flat monthly price (cents), regulatory tier, whether it needs end-user KYC (Tier 3/4), and whether outbound calling is available (not BIC-blocked). Drives the country picker. Tier-4 countries appear only when enabled.