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-Filenameheader. - 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.
Authentication
API key authentication: send your Zernio API key in the Authorization header, prefixed with Bearer.
Request Body
application/octet-stream
TypeScript Definitions
Use the request body type in TypeScript.
binaryHeaders
URL-encoded original filename.
Responses
Success· the request worked
Errors· the request failed
Pre-review a KYC packet
Advisory dry-run of a regulated-KYC packet before submitting. It 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. It 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.
View a KYC document on file
Stream a document backing a reusable verification, so the account holder can see what's on file before reusing it. The ids are the `documentId` values from GET /v1/phone-numbers/kyc `reusable.options[].details[]`. 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`.