Outbound Starter Endpoint

The template includes a small optional outbound route so you can trigger a Twilio call from your own app without building a bigger campaign system first.

What It Does

• POST /voice/outbound creates an outbound call through the Twilio REST API
• Twilio then requests POST /voice/outbound/twiml
• The Worker returns <Connect><Stream> TwiML
• The same Realtime bridge handles the live conversation
• POST /voice/status receives Twilio lifecycle callbacks

Required Variables

• TWILIO_ACCOUNT_SID
• TWILIO_PHONE_NUMBER
• OUTBOUND_API_TOKEN

If any of those are missing, the outbound starter route returns a configuration error and stays inactive.

Example Request

curl -X POST https://<your-worker-subdomain>.workers.dev/voice/outbound \
  -H "Authorization: Bearer <OUTBOUND_API_TOKEN>" \
  -H "Content-Type: application/json" \
  -d '{
    "to": "+15551234567",
    "machineDetection": true,
    "timeoutSeconds": 30
  }'

Request Body

• to: required destination phone number in E.164 format
• machineDetection: optional boolean
• timeoutSeconds: optional ring timeout from 5 to 60 seconds

Notes

• This is only a starter. It does not include retries, campaign logic, or per-call prompt selection.
• The route uses a simple bearer token so you can put it behind your own app, admin panel, or automation system. Cloudflare Access also has a free tier, and their zero-trust solution is excellent and highly scalable.
• The status callback route is useful for storing outbound call lifecycle events before you build a larger workflow engine.