Error 401: what to do when glm-5.3 fails
A 401 means authentication failed: the request carries no API key, or the key is invalid, deleted or expired.
401 Unauthorized means the request carries no valid credential. The gateway could not identify the caller, so the request never reaches the upstream model. Checking the Authorization header and the key status is the only path forward.
glm-5.3 is served by Z.AI. Everything on this page — triggers, fixes and measured data — is compiled from the real runtime behaviour of this model at the gateway layer.
At this gateway, the most common trigger is: The Authorization header is missing. The recommended first action is: Send the header as Authorization: Bearer followed by your key.
Common causes
- The Authorization header is missing
- The key is misspelled or has stray whitespace
- The key was deleted or disabled on the Tokens page
- A key from another platform was used by mistake
How to fix
- Send the header as Authorization: Bearer followed by your key
- Generate a fresh key on the Tokens page
- Check that you are not using a key from another service
- Verify the key with a minimal curl request
Retry with exponential backoff
The snippet below retries when glm-5.3 returns 401, up to 5 attempts, with an increasing wait plus random jitter so concurrent calls do not retry in lockstep. Read the base URL and API key from environment variables — never hardcode them.
import os, time, random
import requests
BASE = os.getenv("OPENAI_BASE_URL") # e.g. https://<your-gateway>/v1
KEY = os.getenv("OPENAI_API_KEY")
MODEL = 'glm-5.3'
def chat(messages, retries=5):
"""Retry with exponential backoff + jitter."""
for i in range(retries):
try:
r = requests.post(
BASE + "/chat/completions",
headers={"Authorization": "Bearer " + KEY},
json={"model": MODEL, "messages": messages, "stream": True},
timeout=60,
)
if r.status_code == 429 or r.status_code >= 500:
time.sleep(min(2 ** i + random.uniform(0, 1), 30))
continue
r.raise_for_status()
return r.json()
except requests.exceptions.Timeout:
time.sleep(min(2 ** i + random.uniform(0, 1), 30))
raise RuntimeError("gave up after " + str(retries) + " retries")
print(chat([{"role": "user", "content": "hello"}]))Key facts for this model
| API endpoint | https://api.airai.cc/v1 |
|---|---|
| OpenAI-compatible | OpenAI-compatible |
| Vendor | Z.AI |
|---|---|
| Context | 1M |
| Capabilities | Reasoning, Tools, Open Weights |
| API formats | openai, openai-response, openai-response-compact, anthropic, gemini, openai-alpha-search |
| Billing formula | p * 1.4 + cr * 0.26 + cc * 0 + c * 4.4 |
FAQ
Does 401 on glm-5.3 depend on region or node?
Group the errors by time and node first; the pattern is usually obvious once you do. If it only happens in production, it is usually an environment difference, not the model. This model is served by Z.AI, so upstream status follows the vendor’s own announcements. Log the request ID on every failure — it beats the status code when debugging.
Does switching to streaming reduce 401?
The request parameters must change; retrying alone will not help. This is a client-side configuration issue; nothing changes server-side. The 1M context window sets the maximum input per request; anything beyond it is rejected outright. Truncate or summarise long inputs — it noticeably reduces 401.
Does switching to a smaller model reduce 401?
Keep a fallback model ready as well. Building a fallback into the architecture is more reliable than patching errors one by one. This model from Z.AI has several upstream nodes the gateway can switch between. Put the model name in config, so switching upstreams needs no code change.
When glm-5.3 returns 401, is the gateway or the upstream more likely at fault?
This error is unrelated to model capability; it is a gateway-layer issue. It is usually transient and recovers on its own. The capability tags for this model are Reasoning, Tools, Open Weights. If it persists for several minutes, contact platform support to confirm upstream status. Decide account-level versus model-level first; the two need completely different handling.
Other errors on this model
- glm-5.3: error 429 — causes and fixes
- glm-5.3: error timeout — causes and fixes
- glm-5.3: error 500 — causes and fixes
- glm-5.3: error 502 — causes and fixes
- glm-5.3: error 503 — causes and fixes
- glm-5.3: error 504 — causes and fixes
- glm-5.3: error 403 — causes and fixes
- glm-5.3: error 400 — causes and fixes
Other models with the same error
- gpt-5
- claude-opus-5
- gemini-2.5-pro
- deepseek-v4-pro
- grok-4.3
- llama-3.3-70b-instruct
- qvq-max
- qwq-32b
- glm-5
- MiniMax-M3
- kimi-k3
- hy3
- doubao-seed-evolving
- mimo-v2.5
- gpt-4o
- claude-opus-4-6
Data updated: 2026-10-10 15:45