[Bug]: MiniMax API Authentication Fails with 401 - Requires Explicit authHeader Configuration #27600
Description
Summary
Bug Description
Using MiniMax model (e.g., MiniMax-M2.5) results in 401 authentication error on first API call:
HTTP 401: authentication_error: login fail: Please carry the API secret key in the 'Authorization' field of the request header (request_id: xxx)
Environment
- OpenClaw version: 2026.2.23, 2026.2.25
- OS: Windows
Steps to Reproduce
- Configure MiniMax API key in
auth.json - Start OpenClaw gateway
- Send a message via any channel (Telegram, webchat, etc.)
- First API call fails with 401 error
Workaround
Manually adding authHeader: true to openclaw.json resolves the issue:
"models": {
"providers": {
"minimax-cn": {
"authHeader": true,
...
}
}
}
### Steps to reproduce
1. Configure MiniMax API key in system ENV
2. Start OpenClaw gateway
3. Send a message via any channel (Telegram, webchat, etc.)
4. First API call fails with 401 error
### Expected behavior
- `authHeader` should default to `true` for MiniMax provider, OR
- Configuration wizard should prompt users to set this option, OR
- Documentation should clearly mention this requirement
### Actual behavior
First API call to MiniMax fails with 401 authentication error. The API key is correctly configured in auth.json, but the request is missing the Authorization header.
### OpenClaw version
2026.2.23, 2026.2.25
### Operating system
Windows11
### Install method
_No response_
### Logs, screenshots, and evidence
```shell
Impact and severity
No response
Additional information
No response