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.
Authorization
bearerAuth API key authentication - use your Zernio API key as a Bearer token
In: header
Path Parameters
The Telnyx document id (from reusable.options[].details[].documentId).
Response Body
application/pdf
application/json
application/json
"string"Upload a KYC document
Upload ONE document and get back its provider document id, to reference from POST /v1/phone-numbers/kyc via `documents[].documentId`. Send the RAW file bytes as the request body (not base64); put the filename in the `X-Filename` header. Uploading documents one-per-request keeps each request under the ~4.5MB body limit. The document streams straight to the number provider and is not stored by Zernio.
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. 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.