Guides

Step-by-step recipes for the integrations developers ask for most.

Browser Calling with WebRTCYour server mints a 5-minute HS256 SIP token via POST /v1/sip/token and hands it to the browser SDK. The SDK connects to the SIP gateway and places or receives calls attributed to your KES wallet.Build a Call Center with ConferencesBuild a call center queue with the Conference verb. Place callers in a named room, join agents via a separate leg, control mute/unmute via status events, and record the full session.Build a Voice IVRUse the GetDigits, Say, and Dial voice actions to build a multi-level IVR menu. Callers press digits to route themselves; your server reads the posted Digits field and returns the next action set.Claim and Route a NumberBrowse available Kenyan DIDs, claim one to your workspace with a single API call, configure voice_callback_url and events_url routing, then verify inbound call delivery with a test webhook handler.Connect your AI to Sautikit over MCPSetup for the hosted MCP server: sign in from claude.ai or connect an editor with an API key, scoping guidance for agents, money-tool confirmations, and the tool reference.Quickstart: Place a CallFive steps from zero to a live outbound call on Sautikit. Sign up, add KES credit, claim a Kenyan DID, POST to /v1/calls, and verify the signed webhook payload.Record and Stream to S3Use the Record voice action or Dial record attribute to capture call audio. The platform stores recordings in object storage and returns a presigned URL. Stream or copy the file to your own S3.Verify Webhook SignaturesSautikit signs every webhook delivery with HMAC-SHA256. The signature header format is t=<timestamp>,v1=<hex>. Verify using raw body bytes concatenated with a dot and the timestamp.