simon84734
03/09/2025, 7:24 AMVapi Support Bot
03/09/2025, 7:25 AMtransfer-destination-request
is triggered. Here's how to fix it:
1. Check your server response - When Vapi sends a transfer-destination-request, your server must respond with a properly formatted JSON containing the destination details, like:
json
{
"destination": {
"type": "number",
"number": "+1234567890",
"message": "Connecting your call",
"callerId": "+0987654321"
}
}
2. Verify your server URL configuration - Make sure the status-update Server URL is correctly set up to handle these requests and is accessible [from Vapi](https://docs.vapi.ai/server-url).
3. Check server logs - Look for any errors in your server logs when the transfer request is made. Your server might be failing to process the request or returning an incorrect format.
4. Test your endpoint - Try manually sending a test request to your endpoint to ensure it responds with the proper destination format.
The status-update Server URL error (400) in your second image suggests that your server might be returning an invalid response or no response at all when Vapi tries to get the transfer destination.
Let me know if you need more specific guidance on any of these steps!
Sources:
- [Dynamic Call Transfers](https://docs.vapi.ai/phone-calling/dynamic-call-transfers)
- [Server URL setup details](https://docs.vapi.ai/server-url)CTmun
03/09/2025, 4:09 PMSato Aniah Asahina
03/10/2025, 8:45 PM