8000 Does it support the "Token" plan or only the standard API key? · Issue #1 · AndrewSpec/minimax_tts · GitHub
[go: up one dir, main page]

Skip to content

Does it support the "Token" plan or only the standard API key? #1

Open

Description

@RmG152

Hi—I'm interested in using the integration with a Minimax account on the "Token" plan. Could you confirm:

  • Whether this integration supports authentication via the Token plan (token-based credentials) or requires the standard API key/credentials.
  • If Token support exists, any required configuration differences (example config snippet or fields to use).
  • If Token support is not available, whether there are plans to add it or recommended workarounds.

Thanks!

Activity

  1. AndrewSpec commented on Oct 18, 2026

    @AndrewSpec
    Owner

    Thanks for asking. The integration has no separate “Token Plan” authentication mode: it sends the value entered in the API Key field as Authorization: Bearer to MiniMax’s native voice-list and WebSocket TTS endpoints.
    MiniMax currently lists Speech 2.8 as included in Token Plan and provides a Token Plan subscription key (sk-cp…). You can try entering that subscription key in the integration’s normal API Key field; there are no additional configuration fields or changes required. Use the appropriate region and select a voice as usual.
    Please note that a Token Plan subscription key and a standard pay-as-you-go API key are separate credentials. Token Plan compatibility with these specific native voice endpoints has not yet been independently tested by this integration, so consider this best-effort support for now.
    If setup validation or TTS fails, please share the redacted error message, selected region, and model/voice ID (never the key). I can then investigate and document or add explicit support if MiniMax requires a different flow.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions

      0