@Matias ok good to know, very odd you are getting an error related to network protocols if you are on cloud 
Good catch 
Switched those from url params to headers and still have a 400 error.
I was digging through the forums and found that another user was able to fix this issue by changing their auth.
Are you using custom auth? In the resource you might need to set it as BEARER {{token.value}} 
If that doesn't work, you might need to come in to office hours and we can try to live troubleshoot/debug.
One last thought, can you screenshot the query metadata from the state tab when you are running the query with the params in the query input field vs when you add the params to the connection UI and run a get from there?
You can find the metadata by clicking the state tab on the left then using the three row symbol below the word 'state' to select the query in question.
