Move a number to another profile
Move a provisioned number to a different profile.
A number is not a single record. Alongside the number itself there are
hidden telephony owner accounts (platform phone, plus sms when SMS is
enabled) and, once WhatsApp is connected, the whatsapp account. They all
carry a profileId and this endpoint moves them together.
Use this instead of PATCH /v1/accounts/{accountId}: that one 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.
id is the number record id from GET /v1/phone-numbers, not an account id.
A profile holds at most one account per platform, so the destination must be free of every platform this number occupies.
Authorization
bearerAuth API key authentication: send your Zernio API key in the Authorization header, prefixed with Bearer.
In: header
Path Parameters
WhatsAppPhoneNumber id.
Request Body
application/json
TypeScript Definitions
Use the request body type in TypeScript.
Response Body
application/json
application/json
application/json
{ "message": "string", "profileId": "string", "movedPlatforms": [ "string" ]}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, Meta rejects that with error 133005, and 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.
Request a Meta re-verification code for a BYO WhatsApp number
For a bring-your-own WhatsApp number (its own WABA, migrated off another BSP) that Meta demoted to re-verification, this requests a new OTP from Meta. The code lands on the customer's own handset, so verifying it is necessarily self-service; call POST /v1/accounts/{accountId}/whatsapp/verify-code with the code once it arrives. Rate-limited to one request per 10 minutes per account, and Meta enforces its own cooldown on top of that.