{"reason": "NOT_ENABLED"}

I'm seeing the same error as well.

The API worked OK for 3 months, but as of this morning (September 1) it is dead.

The error message is "very useful":

"The operation couldn't be completed. (WeatherDaemon.WDSJWTAuthenticatorService.Errors error 1.)"

Has something changed? Do I need to set something somewhere?

I had the same issue today. What worked for me was going to "Certificates, Identifiers & Profiles" and creating a new key and Service ID identifier (instead of using App ID previously).

There was a transient issue with WeatherKit that's since been resolved:

https://developer.apple.com/system-status/

It's unlikely that changing from App ID to Service ID helped to avoid the issue . More likely, it was just that a couple of hours elapsed before you tried again.

If you see a 401 error, that means you failed to authorize, but not necessarily that your token is invalid. When you see such errors, I recommend that you:

1. Check the system status at https://developer.apple.com/system-status/.
2. File a report via Feedback Assistant: https://developer.apple.com/bug-reporting/
3. Start a new thread here in the developer forums (or post in an existing thread, if some has very recently started a new one.)

Hi, we got this error again today, we don't change any code which run fine for months, please help

Just found the reason, when accessing to Apple server, we got this error SSL routines:SSL3_READ_BYTES:tlsv1 alert internal error This could be due to our openSSL or curl is too old, we change another server and it get fixed. Wait for few more days to confirm again

This error is showing up in around 10% of our calls