interface is broken

The problem here is that is an allowed URL but what we need is

A second issue that may come up is that we need to send a URL like "{338728}?apikey=4uGToG7VxxwVnHTdGhpGo3m40nu0HXv8" but it looks like the {} makes it an invalid URI.

Also, is broken.

I get back "Invalid URI,us&appid=dbf2c8f5c77238a1d8d2d0e788bd5e6b" as the content.

curl says the URI is just fine:

jdonwells@penguin:~$ curl ",us&appid=dbf2c8f5c77238a1d8d2d0e788bd5e6b"
{"coord":{"lon":-83.38,"lat":42.4},"weather":[{"id":501,"main":"Rain","description":"moderate rain","icon":"10n"},{"id":701,"main":"Mist","description":"mist","icon":"50n"}],"base":"stations","main":{"temp":284.45,"feels_like":282.47,"temp_min":283.15,"temp_max":285.37,"pressure":1000,"humidity":87},"visibility":4828,"wind":{"speed":2.6,"deg":130},"rain":{"1h":1.15},"clouds":{"all":90},"dt":1586752877,"sys":{"type":1,"id":3869,"country":"US","sunrise":1586775280,"sunset":1586823161},"timezone":-14400,"id":0,"name":"Livonia","cod":200}

Have you reported these problems to

No. That isn’t how it works. It has to be posted here first. If it looks like an actual problem then someone in the inner circle will send it to the development team.

@jdonwells Thank you for alerting us about this problem. Please open a ticket at You necessarily don’t have to post here first if you know something is broken. The post has been passed on to a team member. Expect a response soon.

You have to look at it from a developer’s point of view. 99% of issues are going to be user error. They don’t need to look at all those. So has an automated reply that says to post it here first for public review. If that review reveals a problem then they will accept it. There is nothing wrong with that so long as everyone knows that is the process.