Good Morning Vapi Team, I had a demo and call scheduled this morning with Peter Kakoma, but unfortunately, he was unable to attend either session. We’re currently exploring a proof of concept (POC) using your voice bot services and would appreciate the opportunity to connect and move forward. We have already set up a test account and begun building out assistants and workflows. However, we've encountered two key issues where we could use your support: API Integration: We’re attempting to perform a data dip into our system to retrieve a bearer token, which we then use to access caller-specific account information. Unfortunately, this is not functioning as expected in our tests. We would appreciate assistance troubleshooting this. Squads/Assistant Transfers: We’d like to implement silent transfers between assistants, as outlined in your documentation (link). However, the options described do not appear to be available in our dashboard, and it seems this may relate to a previous version of Vapi. We’d be grateful if we could schedule a call as soon as possible to address these issues and align on next steps for the POC. Looking forward to your response.

Thank you for sharing the details. To help troubleshoot your API integration issue: Could you provide the specific error message or behavior you’re seeing when attempting to retrieve the bearer token during your data dip? This will help us identify whether the problem is with the API call, authentication, or integration setup. Once we have this information, we can offer more targeted support. Sources: - [Silent Transfers](https://docs.vapi.ai/squads/silent-transfers) - [Custom LLM Tool Calling Integration](https://docs.vapi.ai/customization/tool-calling-integration)

I dont believe its allowing x-www-form-urlencoded format. However when I run the function I get this cache-control: no-cache, no-store, max-age=0, must-revalidate content-length: 153 content-type: application/json;charset=utf-8 expires: 0 pragma: no-cache

responded you on email.