About Zapier Community
New to our Community? Get to know more about our space and how to make the most of your time here.

Code of Conduct Community FAQ's Zapier Common Questions What to Expect

Get Started With Zapier
New to Zapier? We have got you covered with our Zapier 101 Resources.

Zapier Essentials

Get Support
Have a question? Let's get you an answer!

How Do I...? Troubleshooting Code & Webhooks Developer Zone

Other Help Resources
Wait, there's more! Check out these Community sourced spaces for additional resources.

Zapier Help Center Hire an Expert

Zapier Products
Learn more about Zapier's new products.

Zapier Tables Zapier Interfaces

Zapier Reading
All of our best learning resources can be found here.

Featured Articles Show & Tell AI Hub Zapier Tools Hub

Learning Groups
Excited to meet other builders? Check out our interest areas full of doers, dreamers, and in-betweeners.

User Groups

Other Learning Resources
Some of our favorite additional ways to upskill your Zapier knowledge.

Zapier Learn Zapier Blog Zapier Webinars

Product Updates
Check out what is new and upcoming with Zapier with our regular product updates.

Product Updates

Early Access Program
Want to join Early Access? Learn more here.

Question

Radio.co error: Got 400 calling POST https://studio.radio.co/api/v1/zapier/stations, expected 2xx.

  • 9 February 2023
  • 3 replies
  • 46 views
I

Hello

I am trying to set up a Zap so that when I add a new track in Spotify, the track is added to my Radio.co account but I receive an error each time. The Radio.co account is fully subscribed.

I get the following error:

Got 400 calling POST https://studio.radio.co/api/v1/zapier/stations, expected 2xx.

Any ideas?

Thanks. 

This post has been closed for comments. Please create a new post if you need help or have a question about this topic.

3 replies

SamB
Rank
Userlevel 7
Badge +11

Hey there @Ibiza Sonica, welcome to the Community! 👋


That’s odd, are the audio files from Radio.co quite large?  

You mentioned that the tracks are being added to Spotify, despite that 400 error. So I’m wondering if the issue is that it’s taking longer than expected to upload the file, due to its size. Meaning we get back that 400 response as it’s not been able to complete the upload in that time. Do you think that could be the case here?

Are you able to test this theory out by uploading a smaller file to see if that gets added by the Zap without running into any errors? Looking forward to hearing from you!

I

Hey Sam!! :)) nice to meet you

Many thanks for your answer,I did what you told me with a smaller file, and the zap  gave me this error

The app returned "cURL error 6: Could not resolve host: True (see https://curl.haxx.se/libcurl/c/libcurl-errors.html)".

Do you know why this can happen? I don't know if I'm doing something wrong

 

Many thanks for your help

Danvers
Userlevel 7
Badge +12

Hi @Ibiza Sonica!

Can I double-check that I understand what you’re trying to do? Is your Zap set up as:

  1. Trigger: Spotify - New Track Added to Playlist
  2. Action: Radio.co - Upload a Track When a New File Is Added

I can see that the Radio.co action needs the url of a track to upload it. I’m not familiar Radio.cc, do you know if you can add tracks using Spotify urls (ie if you do it manually)? Or does it need to be a link to a file (eg the url of a file in Google Drive/Dropbox)?

I took a look at the Radio.cc help docs about adding media and it mentioned using an FTP server, but I’m not sure if that’s applicable here. 

I hope that helps to get you pointed in the right direction, let us know if you have any questions!

Terms & Conditions