Build a draft inbound IVR flow.
Plan the caller journey with a greeting, digit collection, menu branches and a transfer target. The customer IVR API stores a draft flow for your account. Binding an assigned inbound number to that draft records the intended route; carrier routing must be configured separately before live calls can use it.
Make each step understandable.
A short greeting tells callers where they are. A menu can offer a small set of choices, collect digits and transfer to a SIP line or number. Keep prompts short, give callers an escape or fallback path, and test every branch before publishing any routing with a carrier.
The builder accepts play, collect, menu and transfer steps, and can attach account-owned audio to a play step. Drafts are account-scoped. Session history is available when calls are actually recorded by the integration; creating a flow does not create call traffic.
Save a draft, then bind an assigned DID.
Use a Bearer key with ivr:write to create a flow at POST /api/v1/ivr/flows. The response identifies a draft. Once an inbound number is assigned, PATCH /api/v1/ivr/dids/{did}/bind attaches its flow_id. Number ownership and flow ownership are checked on the server.
POST /api/v1/ivr/flows
Authorization: Bearer YOUR_API_KEY
Content-Type: application/json
{"name":"Main menu","steps":[{"type":"play","prompt":"Welcome. Choose an option."},{"type":"collect","digits":1},{"type":"transfer","target":"support-line"}]}Protect callers and set expectations.
Announce recording if recording is enabled and required for your destination. Avoid collecting payment credentials or other sensitive data in basic digit prompts. Confirm local calling, accessibility and privacy requirements before deploying a live menu. Carrier publishing is not connected in this build.
Understand inbound number setup