401 unauthorized for dev.to/api/articles/me

Describe the bug

Newly generated API keys are not able to authenticate against the DEV API.

Every request to authenticated endpoints (for example /api/articles/me) returns 401 Unauthorized, even when using a freshly generated API key.

Public API endpoints continue to work as expected.

To Reproduce

1. Log in to DEV.
2. Generate a new API key in Account Settings.
3. Make a request to an authenticated endpoint, for example:

curl -i \
  -H "api-key: YOUR_API_KEY" \
  https://dev.to/api/articles/me

1. Observe that the response is 401 Unauthorized.

Expected behavior

A valid, newly generated API key should successfully authenticate the request and return the authenticated user's articles (or an empty list if none exist), instead of returning 401 Unauthorized.

Desktop

• OS: macOS
• Browser: Chrome

Additional context

• The same behavior occurs with multiple newly generated API keys.
• The request includes the api-key header as documented.
• The issue is reproducible using both application code and curl, so it does not appear to be client-library related.
• Public API endpoints (such as /api/articles) continue to work normally, suggesting the issue is specific to API key authentication.