Been seeing 404s for the last couple of days ://

Experiencing the same here, started ~2 days ago

My experience has been when sending a request without the timezone that the response defaults to the timezone at the requested lat and long, which is the desired behavior for my use case. That being said, as you mentioned, the documentation states that timezone is a required query param and given the API is still in beta and past behavior by the WeatherKit devs I wouldn't be surprised if they decided to start failing all requests made without a timezone without warning at any point in the future. I am working on adding timezone to my queries but would love for it to be optional and defaulting to the timezone at the lat and long (like DarkSky).

I feel the same way, would love to have the timezone at location by default

Same issue over here, whereas DarkSky is doing just fine

I have been experiencing the same issue with my product, intermittent 401's with a NOT_ENABLED message

I am experiencing the same thing