Vernon

1. elon saw someone posting about how all of the bots he hates steal API keys from official clients anyway;
2. he understands just enough about computers to know that the secrets on twitter's official apps should be rotated, so he stormed into the moderation office to order that;
3. this failed to get communicated to the product teams and it went through without their approval, under the idea that either the official apps don't use the API for anything loadbearing or that rotating the secrets should be an unnoticeably quick process;
4. that idea is very very false;
5. we're watching them learn this

Here's the error message I got when trying to DM.

The Twitter developer page says this about that error message (as error code 37 is something else, apparently):

Code 220
Your credentials do not allow access to this resource.
Corresponds with HTTP 403. The authentication token in use is restricted and cannot access the requested resource.

So yes, API keys were indeed restricted lmao

(Error code 37 seems to mean "Not authorized to use this endpoint" according to the Twitter Community forums, which is an inaccessible webpage which is conveniently cached in google search results though. More confirmation that it's API issues though!)