API2 always returns 401 Unauthorized with valid Access Tokens

1

I created multiple Access Tokens from:

Settings → Access Tokens

I copied each token immediately after creation and tested it with both curl and my own extension.

Example:

curl -v -H "X-API-KEY: <my_access_token>" http://localhost:8080/api2/businesses

The request is sent correctly, and I can confirm that the X-API-KEY header is included.

However, every API endpoint returns:

HTTP/1.1 401 Unauthorized

{
  "error": "Unauthorized"
}

I tested:

  • GET /api2/businesses
  • GET /api2/access-tokens
  • GET /api2/version

All return 401 Unauthorized.

Things I have already verified:

  • Running the official Manager Server executable.
  • API documentation is available at /api2, so the API is enabled.
  • Created multiple new Access Tokens.
  • Tested multiple businesses.
  • Tested from curl.
  • Tested from a browser extension.
  • Tested with different browsers.
  • Restarted the server after creating new tokens.

The request always reaches the server, but the server rejects every Access Token with HTTP 401.

My server is started with:

ManagerServer.exe --urls http://localhost:8080 --path "C:\Users\Administrator\Documents\manager"

Is there any known issue with API2 authentication in version 26.7.23.3657, or is there any additional configuration required for Access Tokens?

Thank you.