OpenAI API / OpenAI API

ChatGPT Plus OAuth returns 429 quota exceeded for third-party tool API calls

Understand why ChatGPT Plus quota does not apply to third-party API calls; determine if separate credits required or if quota routing between first-party and third-party OAuth contexts is a product bug Includes evidence for OpenAI API troubleshooting demand.

Source-backed Last updated May 19, 2026 1 source Needs local verification

Category: OpenAI API
Error signature: 429 quota exceeded — ChatGPT Plus OAuth authentication succeeds but third-party Codex calls to openai-codex/gpt-5.4 return 429 despite active Plus subscription
Quick fix: Reduce request pressure, check quota or plan limits, and retry with backoff instead of immediate repeated requests.
Updated: May 19, 2026
Verification status: Source-backed
Evidence: 1 public source URL

Before you change production

This page includes public source URLs in the imported troubleshooting record. Compare those references with your version and environment before applying changes.

Reproduce the smallest failing action and save non-secret logs before changing configuration.
Check versions for OpenAI API, related SDKs, package managers, CI runners, and hosting providers.
Change one setting or dependency at a time, then rerun the same failing command or request.
Avoid destructive commands, credential rotation, billing changes, or security relaxations without a rollback plan.

What this error means

429 quota exceeded — ChatGPT Plus OAuth authentication succeeds but third-party Codex calls to openai-codex/gpt-5.4 return 429 despite active Plus subscription is a OpenAI API failure pattern reported for developers trying to understand why chatgpt plus quota does not apply to third-party api calls; determine if separate credits required or if quota routing between first-party and third-party oauth contexts is a product bug. Based on the imported evidence, treat this as a tool-specific troubleshooting page rather than a generic API error.

Why this happens

GitHub Issue #2951 in openai/openai-python (opened Mar 10 2026, AllinAI20260127). OAuth login works perfectly, but API calls via third-party tools get 429 quota. Directly affects paying Plus subscribers using non-Official clients. High commercial impact since it involves billing/quota on a paid subscription product. Category mapping: OpenAI API (quota/billing error on paid API service).

Common causes

GitHub Issue #2951 in openai/openai-python (opened Mar 10 2026, AllinAI20260127). OAuth login works perfectly, but API calls via third-party tools get 429 quota. Directly affects paying Plus subscribers using non-Official clients. High commercial impact since it involves billing/quota on a paid subscription product. Category mapping: OpenAI API (quota/billing error on paid API service).

Quick fixes

Confirm the exact error signature matches 429 quota exceeded — ChatGPT Plus OAuth authentication succeeds but third-party Codex calls to openai-codex/gpt-5.4 return 429 despite active Plus subscription.
Check the OpenAI API account, local tool state, and provider configuration involved in the failing workflow.
Reduce request pressure, check quota or plan limits, and retry with backoff instead of immediate repeated requests.

Platform/tool-specific checks

Verify the command, editor, extension, or API client that produced the error.
Compare local settings with CI, deployment, or editor-level settings when the error appears in only one environment.
Avoid deleting credentials, local model data, or project settings until the failing scope is clear.

Step-by-step troubleshooting

Capture the exact error message and the command, editor action, or request that triggered it.
Check whether the failure is account/auth, quota/rate, model/provider, local runtime, or deployment configuration.
Review the source evidence below and compare it with your environment.
Apply one change at a time and rerun the smallest failing action.
Keep the working fix documented for the team or deployment environment.

How to prevent it

Keep provider/tool configuration documented.
Record non-secret diagnostics such as tool version, provider name, model name, and command path.
Add a lightweight check before CI or production workflows depend on the tool.

Diagnostic flow for this page

Match 429 quota exceeded — ChatGPT Plus OAuth authentication succeeds but third-party Codex calls to openai-codex/gpt-5.4 return 429 despite active Plus subscription exactly before applying the quick fix.
Compare the failing environment with OpenAI API versions, account scope, provider settings, and deployment context.
Check the listed common causes in order, starting with the cause that best matches your logs.
Use the evidence status below to decide whether to confirm against public sources or official documentation.
Apply one reversible change, rerun the smallest failing action, and keep rollback notes.

FAQ

What does 429 quota exceeded — ChatGPT Plus OAuth authentication succeeds but third-party Codex calls to openai-codex/gpt-5.4 return 429 despite active Plus subscription mean in OpenAI API?

429 quota exceeded — ChatGPT Plus OAuth authentication succeeds but third-party Codex calls to openai-codex/gpt-5.4 return 429 despite active Plus subscription indicates the workflow described by "ChatGPT Plus OAuth returns 429 quota exceeded for third-party tool API calls" failed in a OpenAI API context. Start by confirming the exact signature and the component that emitted it.

What should I check first for 429 quota exceeded — ChatGPT Plus OAuth authentication succeeds but third-party Codex calls to openai-codex/gpt-5.4 return 429 despite active Plus subscription?

Check whether this cause matches your environment: GitHub Issue #2951 in openai/openai-python (opened Mar 10 2026, AllinAI20260127). OAuth login works perfectly, but API calls via third-party tools get 429 quota. Directly affects paying Plus subscribers using non-Official clients. High commercial impact since it involves billing/quota on a paid subscription product. Category mapping: OpenAI API (quota/billing error on paid API service).

Is the 429 quota exceeded — ChatGPT Plus OAuth authentication succeeds but third-party Codex calls to openai-codex/gpt-5.4 return 429 despite active Plus subscription guidance source-backed?

The "ChatGPT Plus OAuth returns 429 quota exceeded for third-party tool API calls" page is labeled source-backed. It has 1 public source URL from github.com, so use that evidence status when deciding how much additional verification you need.

When should I avoid the quick fix for 429 quota exceeded — ChatGPT Plus OAuth authentication succeeds but third-party Codex calls to openai-codex/gpt-5.4 return 429 despite active Plus subscription?

For "ChatGPT Plus OAuth returns 429 quota exceeded for third-party tool API calls", avoid applying "Reduce request pressure, check quota or plan limits, and retry with backoff instead of immediate repeated requests." when the error text differs, the affected version or provider is different, or the change would touch credentials, billing, DNS, production deploy settings, or irreversible data.

What should I collect before debugging 429 quota exceeded — ChatGPT Plus OAuth authentication succeeds but third-party Codex calls to openai-codex/gpt-5.4 return 429 despite active Plus subscription?

For "ChatGPT Plus OAuth returns 429 quota exceeded for third-party tool API calls", collect the failing OpenAI API command or request, non-secret configuration, versions, timestamps, request IDs when available, and the smallest reproduction that still triggers the signature.