Create a hosted KYC link
Create a single-use, 7-day hosted KYC link that your end customer completes WITHOUT a Zernio login. Useful when the person who holds the ID and address is not your team. They fill the regulated verification on a Zernio-hosted page; the number provisions under YOUR account once they submit. Only regulated (KYC) countries are valid: a country that does not require KYC returns 400.
Pass numberType (local, mobile, national, toll_free) to choose
which of the country's offered types the shared form collects KYC for and
eventually orders; omitted defaults to the country's default type (which
may be national and therefore have no inventory in a geographic area
code). Pass areaCode (NDC digits) to constrain the eventual order to a
specific area; it is validated against the chosen numberType.
White-label the page with branding (your company name, logo, brand
color). Supply redirect_url to send the end customer back to your own
site after a successful submit (completion params are appended; see
below). Listen for the whatsapp.number.kyc_submitted webhook to react
when the form is completed.
Authorization
bearerAuth API key authentication: send your Zernio API key in the Authorization header, prefixed with Bearer.
In: header
Request Body
application/json
TypeScript Definitions
Use the request body type in TypeScript.
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.createPhoneNumberKycLink({ body: { profileId: 'profile_abc123', country: 'string', },});console.log(data);{ "url": "string", "token": "string", "expiresAt": "2019-08-24T14:15:22Z"}View a KYC document on file
Stream a document backing a reusable verification (the `documentId` values from GET /v1/phone-numbers/kyc `reusable.options[].details[]`), so the account holder can see what's on file before reusing it. Returned inline as `application/pdf` (uploads are normalized to PDF). Auth-scoped: a document is viewable only when its id is referenced by one of the caller's own numbers. Otherwise `404`.
Get declined requirements
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 only those, because 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.