Register a connected WhatsApp number on the Cloud API
Re-runs Meta's Cloud API registration for a WhatsApp account that is already connected.
Use it when the number has its own two-step verification PIN. The connect flows register with a default PIN, and Meta rejects that with error 133005.
The number then fails every send with the misleading '(#200) You do not have the necessary permission to send messages' while the account still shows as connected.
The PIN is used for this call only and is not stored.
Authentication
API key authentication: send your Zernio API key in the Authorization header, prefixed with Bearer.
Path parameters
The WhatsApp account ID
Body
application/jsonOptional parameters1 field
The 6-digit two-step verification PIN set on the number. Omitting it applies Zernio's managed default registration PIN, the same one every Embedded Signup connect sets automatically.
Responses
Success· the request worked
Errors· the request failed
Get number status
Live snapshot of a connected number straight from Meta. ### Phone-number node - display number - display name + approval - quality rating - messaging-limit tier - throughput - official-business badge - connection status - health_status ### Owning WhatsApp Business Account - name - business verification - timezone - health_status ### Why live It is fetched live because Meta updates quality/tier/name/health over time. The call also refreshes the cached values shown on the connection card.
Move a number to another profile
Move a provisioned number to a different profile. A number is not a single record. These all carry a profileId, and this endpoint moves them together: - the number itself - hidden telephony owner accounts (platform `phone`, plus `sms` when SMS is enabled) - the `whatsapp` account, once WhatsApp is connected ### Why not `PATCH /v1/accounts/{accountId}` That endpoint moves the account only and leaves the number itself pinned to its original profile, which splits the number across two profiles. Connecting a Zernio-provisioned number from any profile but its own is rejected with a `409` (`WHATSAPP_NUMBER_PINNED_TO_PROFILE`). This endpoint is how you re-home the number first, so it can then be connected from the new profile. ### Notes - `id` is the number record id from `GET /v1/phone-numbers`, not an account id. - The destination profile may already hold other numbers.