Toggle recording for a number's WhatsApp calls
Sets the SautiKit-side "record WhatsApp calls" flag. This is a SautiKit setting, not a Meta one: Meta's native call recording is available only on its Cloud/WebRTC calling path, which a BYOC SIP integration cannot use, so recording is captured on our own SIP media leg instead.
Authorization
bearerAuth Long-lived ES256 JWT minted from the dashboard (https://app.sautikit.com/developers/api-keys). Signed by the
platform keyring. Carries workspace_id and scopes claims;
revoked via the platform deny-list.
In: header
Path Parameters
The tenant NUMBER id.
uuidRequest Body
application/json
TypeScript Definitions
Use the request body type in TypeScript.
Response Body
application/json
application/json
application/json
curl -X PUT "https://example.com/v1/numbers/497f6eca-6276-4993-bfeb-53cbbbba6f08/whatsapp/recording" \ -H "Content-Type: application/json" \ -d '{ "enabled": true }'{ "recording_enabled": true}{ "error": { "code": "validation.bad_request", "message": "string", "request_id": "string", "details": [ "string" ] }}{ "error": { "code": "validation.bad_request", "message": "string", "request_id": "string", "details": [ "string" ] }}Update a number's WhatsApp call settings PUT
Writes call hours, icon visibility, callback permission, and voicemail behaviour to Meta, then persists what was written. Synchronous — unlike enable/rotate, this returns `200` only after Meta has accepted the write. The write never includes `calling.sip`, so it cannot disturb the provisioned trunk.
Toggle transcription for a number's WhatsApp calls PUT
Sets the SautiKit-side "transcribe WhatsApp calls" flag. Like recording, this is SautiKit-side speech-to-text over our own SIP media leg — Meta's native transcription is Cloud/WebRTC-only and unavailable to a BYOC SIP integration.