litellm - 💡(How to fix) Fix [Bug]: GLM Coding plan uses standard GLM api instead of coding [1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
BerriAI/litellm#25479Fetched 2026-04-11 06:14:05
View on GitHub
Comments
0
Participants
1
Timeline
2
Reactions
0
Author
Participants
Timeline (top)
labeled ×2

Error Message

Actual api base uses non coding endpoint by default. Will 429 error even if credits are available

RAW_BUFFERClick to expand / collapse

Check for existing issues

  • I have searched the existing issues and checked that my issue is not a duplicate.

What happened?

GLM website: Note: When using the GLM Coding Plan, you need to configure the dedicated Coding endpoint - https://api.z.ai/api/coding/paas/v4 instead of the general endpoint - https://api.z.ai/api/paas/v4 Note: The Coding API endpoint is only for Coding scenarios and is not applicable to general API scenarios. Please use them accordingly.

Actual api base uses non coding endpoint by default. Will 429 error even if credits are available

Steps to Reproduce

  1. purchase glm coding
  2. configure in yaml
  3. try using it

Relevant log output

What part of LiteLLM is this about?

Proxy

What LiteLLM version are you on ?

1.81.14

Twitter / LinkedIn details

No response

extent analysis

TL;DR

Update the API base to use the dedicated Coding endpoint to resolve the 429 error.

Guidance

  • Verify that the GLM Coding Plan is correctly configured in the YAML file to use the Coding endpoint https://api.z.ai/api/coding/paas/v4.
  • Check that the API base is not defaulting to the general endpoint https://api.z.ai/api/paas/v4, which may cause the 429 error.
  • Ensure that the credits are available and sufficient for the Coding scenario.
  • Review the documentation for the GLM Coding Plan to confirm the correct configuration and usage.

Notes

The issue seems to be related to the incorrect usage of the API endpoint. The provided information does not include any log output, which might be helpful in further troubleshooting.

Recommendation

Apply workaround: Update the API base to use the dedicated Coding endpoint, as this is likely to resolve the 429 error and allow the correct usage of the GLM Coding Plan.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING