Vapi is the Voice AI platform for developers.

Vapi AI

Guys, when you change something in the system, please send an email and at least a bit of time to adjust; 
the recording URL is completely differnt and this has caused all our new application to fail.

<@1247423790946713693>
I'm truly sorry to hear about the inconvenience caused by the changes to the recording URL. Your feedback is extremely valuable, and I understand how important it is to have clear communication about system updates. I'll make sure to pass on your message to ensure better handling of such updates in the future. In the meantime, can I assist you with updating your applications to work with the new recording URL format?

You can continue this conversation by mentioning me in the message.

I don't need to ask for help, however this is the second time things have changed and we have customers getting upset.

This time I would like to get contacted in private; As we do have customer complaining and also advertisment running with people not able to listen/try the most important part.

Hey <@1247423790946713693> can you share more about your expectations, what is change according to you and what was it previously?

> advertisment running with people not able to listen/try the most important part.

Can you explain more on this?


https://cdn.discordapp.com/attachments/1306893521894113280/1308005000877707314/image.png?ex=673c5e15&is=673b0c95&hm=a0748def43af45741d6510e956dad6bd03db8cfe8b16694f9ffdb2940409d27e&

Before you were using the auth.vapi.ai and now is storage.vapi.ai 

It seems like you have opted in for the vanity domain in supabase

and that destroyed our pipeline to provide smaller audio files to customers (we are convertin in mp3 as we have people using 'not so ideal' internet connection)

I know there is no contract for that field; however change like this would be good to be underlined at least in an email for developers 🙂

Hey <@1247423790946713693> I am really sorry for the bad experience, honestly speaking I never thought you were dependant on this url.

As you have already said there is no contract for this, and we didn't expected anyone to use url paths for one of their use cases.

Our bad too, there is no contract that specifcy that the recordingUrl would always be the same; However it would be great to have a dev-email vs product-email too!

Anyway thanks for looking into this Shubham, you can close the ticket; At that time we had one of our biggest client trying out the platform and unluckly enough we did the demo when this url changed

I believe your capturing call-Id from the recording url correct?

Correct, as i'm re-using that ID to get the Mp3 from my side

you can store the recordingURL directly instead of being dependant on it and can use callID as one of the primary keys, what's your though on this.

we have couple of people that have complained about the audio size (the download speed), however it's something on their end using bad connection; Therefore we decided to do a mp3 conversion