Update calling config
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.
API key authentication - use your Zernio API key as a Bearer token
In: header
Path Parameters
Response Body
application/json
import Zernio from '@zernio/node';const zernio = new Zernio({ apiKey: process.env.ZERNIO_API_KEY });const { data } = await zernio.whatsappcalling.updateWhatsAppCalling({ path: { id: 'abc123', }, body: { accountId: 'account_abc123', },});console.log(data);{
"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).
Disable calling on a number DELETE
Disable calling. Sends calling.status=DISABLED to Meta (best-effort) and flips the local `callingEnabled` flag off. forwardTo and SIP creds are preserved so a re-enable does not lose the destination.