mirror of
https://github.com/langgenius/dify-official-plugins.git
synced 2026-07-22 01:55:27 -04:00
Minimax plugin returns "No choices in response" despite valid API base and credentials #780
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @emuchogu on GitHub (Nov 5, 2025).
Self Checks
Dify version
1.9.2
Cloud or Self Hosted
Self Hosted (Docker)
Steps to reproduce
When configuring the Minimax plugin from here:
https://marketplace.dify.ai/plugins/langgenius/minimax?source=http%253A%252F%252Fbizwiz-suse.lab&theme=system
I receive the following error in Dify:
No choices in response
API Base used:
https://api.minimaxi.com
Using Python with the same credentials works without issues:
import os
os.environ['ANTHROPIC_BASE_URL'] = 'https://api.minimax.io/anthropic'
os.environ['ANTHROPIC_API_KEY'] = 'eyJhbGci......'
I obtained my API key from:
https://platform.minimax.io/login
instead of:
https://platform.minimaxi.com/login?redirect=%2Fuser-center%2Fbasic-information%2Finterface-key
because I do not have a Chinese phone number to register.
Note: setting the API base to
https://api.minimax.ioalso fails in the Dify plugin with the same error.✔️ Expected Behavior
Should add minimax model provider
❌ Actual Behavior
Fails with alert:
No choices in response
@dosubot[bot] commented on GitHub (Nov 5, 2025):
Hi @emuchogu! I'm Dosu and I’m helping the dify team.
The "No choices in response" error from the Minimax plugin usually means the plugin didn't find a
choicesfield in the API response. The plugin's code explicitly checks for this field and raises this error if it's missing. This is a common issue with OpenAI-compatible plugins in Dify: they expect the response to strictly follow the OpenAI schema, including a top-levelchoicesarray with message content. If the Minimax API returns a different structure, or if your account/subscription doesn't allow text LLM calls (for example, if you only have TTS credits), you'll get this error—even if your API key works in Python for other endpoints or models.Some users have found that new free Minimax accounts may have a small balance for text model requests, but audio-only or zero-balance accounts will fail with "No choices in response" when the plugin tries to validate credentials or call the text LLM. You can confirm this by checking your Minimax account balance and subscription type, and by inspecting the raw API response (e.g., via logs or Postman) to see if it contains the expected
choicesfield or an error message like "Insufficient Balance" citation.If your API responses are valid and contain
choicesbut the plugin still fails, it's possible the response format differs slightly from what the plugin expects. In that case, you may need to patch the plugin to handle the actual response structure, or log the full response for debugging citation.Other possible causes include stricter timeout and credential validation logic in recent Dify versions, or network issues in Docker setups. Checking plugin daemon and Docker logs can help pinpoint the problem citation.
In summary: double-check your Minimax account's subscription/balance for text LLM usage, inspect the actual API response for the
choicesfield, and review plugin logs for more details. If the API response format is different, the plugin may need to be updated to handle it.To reply, just mention @dosu.
How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other
