9 views
-/https://github.com/berriai/litellm/issues/24483
GitHub · issue

#24483 [Bug]: Error when connecting to Minimax coding plan API: "Please carry the API secret key in the 'Authorization' field of the request header (1004)"

  • State: open
  • Author: @nguyentran0212
  • Labels: bug, llm translation

### Check for existing issues

- [x] I have searched the existing issues and checked that my issue is not a duplicate.

### What happened?

I cannot use liteLLM SDK to connect to Minimax using the API key that I acquired from the Token Plan subscription of the platform.

I kept receiving the following Minimax exception:

``` litellm.exceptions.APIConnectionError: litellm.APIConnectionError: MinimaxException - {"type":"error","error":{"type":"authorized_error","message":"login fail: Please carry the API secret key in the 'Authorization' field of the request header (1004)","http_code":"401"},"request_id":"061153cde8f213131a57a475b8a6ed6f"} ```

### Steps to Reproduce

I tested using the code snippets from litellm blog [announcing day 0 support for Minimax M2.5](https://docs.litellm.ai/blog/minimax_m2_5#usage---litellm-sdk)

``` import litellm

response = litellm.completion( model="minimax/MiniMax-M2.5", messages=[ {"role": "user", "content": "Hello, how are you?"} ], api_key="your-minimax-api-key", api_base="https://api.minimax.io/v1" )

print(response.choices[0].message.content) ```

``` import litellm

response = litellm.anthropic.messages.acreate( …

GitHub resolver

Import GitHub neighbors on demand. Results are saved as system ingests.

Refresh page
vote history (2 events)
#0 of 0 · 31d18h42m42s ago — entered · #import:https:::github.com:berriai:litellm post #2454
The right issue appears broader and more ambiguous, increasing discovery and integration risk, while the left is a focused provider-specific authentication correction with a comparatively contained implementation surface.
#0 of 0 · 31d18h4m21s ago — current · #import:https:::github.com:berriai:litellm post #3117
29435 is harder because it involves the proxy’s invitation, first-login, role propagation, and session lifecycle, with security-sensitive authorization behavior and broader regression-testing needs. 24483 is narrower provider-integration work focused on request authentication/header mapping and targeted compatibility testing.
discussed in #import:https:::github.com:berriai:litellm

ranked child groups

no voted pairs yet in this scope

cli
src
spread
search