Enable calling on a number
Enable WhatsApp Business Calling on a connected number. Configures Meta calling.status=ENABLED with our Telnyx SIP endpoint, fetches and stores the Meta-issued SIP password (encrypted), and snapshots the customer's forward-to destination.
API key authentication - use your Zernio API key as a Bearer token
In: header
Path Parameters
WhatsAppPhoneNumber Mongo ID
tel:+E164 / sip:... / wss://... destination
Stored encrypted, never returned by any endpoint.
falseResponse Body
application/json
application/json
import Zernio from '@zernio/node';const zernio = new Zernio({ apiKey: process.env.ZERNIO_API_KEY });const { data } = await zernio.whatsappcalling.enableWhatsAppCalling({ path: { id: 'abc123', }, body: { accountId: 'account_abc123', forwardTo: 'string', },});console.log(data);{
"success": true,
"callingEnabled": true,
"sipHostname": "string",
"forwardTo": "string"
}{
"error": "Unauthorized"
}Get calling config for an account GET
Returns the local calling configuration snapshot for the connected WhatsApp account: whether calling is enabled, the forward-to destination URI, recording opt-in state, the WhatsAppPhoneNumber doc id (use as `{id}` on the calling-config write endpoints) and whether SIP digest credentials are stored (the encrypted password itself is never returned).
Update calling config PATCH
Update fields on an already-enabled number. Only fields present in the body are written; `undefined` leaves the stored value alone, explicit `null` clears a nullable field. No Meta side effect, this only changes local routing state consumed by the Telnyx webhook handler.