Get a call recording
Resolves a fresh, playable MP3 URL for the call's recording.
Provider-signed recording URLs expire ~10 minutes after signing, so the
recordingUrl stored on the call is usually stale by the time it is
played; this endpoint re-signs on demand. Default responds 302 Found
redirecting to the fresh URL (point an <audio> element or a link
straight at this endpoint); pass as=json to receive { url } instead.
API key authentication - use your Zernio API key as a Bearer token
In: header
Path Parameters
Query Parameters
json returns { url } instead of a 302 redirect.
"json"Response 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.getWhatsAppCallRecording({ path: { id: 'abc123', }, query: { accountId: 'account_abc123', },});console.log(data);{
"url": "string"
}{
"error": "Unauthorized"
}Get calling config for a number GET
The WhatsApp Business Calling configuration of this number, keyed the same way as the POST/PATCH/DELETE below (full read-write on one sub-resource). Encrypted secrets are never returned; only a boolean saying whether a SIP password is stored. The account-scoped read (`GET /v1/whatsapp/calling?accountId=`) remains for callers that only know the social account id, and additionally carries account-level extras (billing eligibility, current-period spend).
Start caller-ID verification for a customer-brought number POST
Customer-brought (BYO) WhatsApp numbers cannot present themselves as caller ID on `tel:` call forwards until verified (carrier anti-spoofing); until then forwarded calls show a Zernio number (`callerIdMode: platform` on the calling config). This sends a one-time code to the number by SMS or voice call. Re-POST to resend. Zernio-purchased numbers never need this and get a 400.