For connection selection and controlled Studio/API testing, use Make an outbound call. This page focuses on the backend dial request and call-event correlation. Voiceflow numbers use the API because they have no Studio Test call panel.
Before you begin
- An assigned Twilio, Vonage, Telnyx or Voiceflow-provisioned number, or a configured SIP connection with outbound enabled.
- Its connection/phone-number ID and a server-side API key authorized for the assigned agent.
- Workspace credits, production concurrency capacity and a test destination you control.
Place and verify a call
Choose the correct contract
Voiceflow-provisioned numbers also support outbound calling. Do not send the phone-number request body to the SIP route.
Send one dial request
Replace the fictional destination with your test number. amd: false disables answering-machine detection for this test. A successful phone-number request returns 201; the SIP operation returns 200. Both have an empty body, not a call ID.
Verify the answered call
Answer the phone and complete the task. If a phone-number request included variables, check the agent uses that expected context; SIP calling does not pass request variables. Correlate the call through call events and its Transcript. HTTP success only means the provider accepted the dial request.
Verify the result
Confirm the correct destination rang, the intended agent answered, any supported context was used as expected, and the final call outcome appears in your receiver or Transcript.
Handle rejected or uncertain requests
On 402, resolve workspace credits; on 429, wait for concurrency capacity. On a timeout or connection loss after sending, inspect provider/call events before dialing again: an unknown HTTP outcome can still have placed a call. No idempotency guarantee is documented for this operation.