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
social 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.
API key authentication - use your Zernio API key as a Bearer token
In: header
Path Parameters
WhatsAppPhoneNumber id.
Destination profile id. Must belong to the same team.
Response Body
application/json
application/json
application/json
import Zernio from '@zernio/node';const zernio = new Zernio({ apiKey: process.env.ZERNIO_API_KEY });const { data } = await zernio.whatsappphonenumbers.moveWhatsAppNumberToProfile({ path: { id: 'abc123', }, body: { profileId: 'profile_abc123', },});console.log(data);{
"message": "string",
"profileId": "string",
"movedPlatforms": [
"string"
]
}{
"error": "string",
"type": "invalid_request_error",
"code": "string",
"param": "string",
"platform": "string",
"platformError": {},
"details": {}
}{
"error": "Unauthorized"
}Revoke a sandbox session DELETE
Hard-deletes the session. The user loses the ability to send to that phone via the sandbox until they re-activate it. Existing conversations and messages already exchanged with that phone are untouched — revocation only blocks FUTURE sends. Sessions belonging to other users cannot be revoked; the response is the same 400 as "session not found" so existence isn't leaked.
Register a connected WhatsApp number on the Cloud API POST
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.