OpenAI API / OpenAI API

ChatGPT Plus OAuth succeeds but third-party tools return 429 quota exceeded

Resolve 429 quota error when using third-party apps with ChatGPT Plus OAuth authentication Includes evidence for OpenAI API troubleshooting demand.

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

Category: OpenAI API
Error signature: OAuth login succeeds → API call returns 429 quota exceeded despite active ChatGPT Plus subscription
Quick fix: Reduce request pressure, check quota or plan limits, and retry with backoff instead of immediate repeated requests.
Updated: May 21, 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

OAuth login succeeds → API call returns 429 quota exceeded despite active ChatGPT Plus subscription is a OpenAI API failure pattern reported for developers trying to resolve 429 quota error when using third-party apps with chatgpt plus oauth authentication. Based on the imported evidence, treat this as a tool-specific troubleshooting page rather than a generic API error.

Why this happens

GitHub issue openai/openai-python#2951 — Auth flow works but quota routing fails for third-party Codex/OAuth integrations. Open since Mar 10 2026, confirmed by multiple commenters. Not in covered-errors.md. Category: OpenAI API — billing/quota routing failure on paid service.

Common causes

GitHub issue openai/openai-python#2951 — Auth flow works but quota routing fails for third-party Codex/OAuth integrations. Open since Mar 10 2026, confirmed by multiple commenters. Not in covered-errors.md. Category: OpenAI API — billing/quota routing failure on paid service.

Quick fixes

Confirm the exact error signature matches OAuth login succeeds → API call returns 429 quota exceeded despite active ChatGPT 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 OAuth login succeeds → API call returns 429 quota exceeded despite active ChatGPT 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 OAuth login succeeds → API call returns 429 quota exceeded despite active ChatGPT Plus subscription mean in OpenAI API?

OAuth login succeeds → API call returns 429 quota exceeded despite active ChatGPT Plus subscription indicates the workflow described by "ChatGPT Plus OAuth succeeds but third-party tools return 429 quota exceeded" failed in a OpenAI API context. Start by confirming the exact signature and the component that emitted it.

What should I check first for OAuth login succeeds → API call returns 429 quota exceeded despite active ChatGPT Plus subscription?

Check whether this cause matches your environment: GitHub issue openai/openai-python#2951 — Auth flow works but quota routing fails for third-party Codex/OAuth integrations. Open since Mar 10 2026, confirmed by multiple commenters. Not in covered-errors.md. Category: OpenAI API — billing/quota routing failure on paid service.

Is the OAuth login succeeds → API call returns 429 quota exceeded despite active ChatGPT Plus subscription guidance source-backed?

The "ChatGPT Plus OAuth succeeds but third-party tools return 429 quota exceeded" 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 OAuth login succeeds → API call returns 429 quota exceeded despite active ChatGPT Plus subscription?

For "ChatGPT Plus OAuth succeeds but third-party tools return 429 quota exceeded", 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 OAuth login succeeds → API call returns 429 quota exceeded despite active ChatGPT Plus subscription?

For "ChatGPT Plus OAuth succeeds but third-party tools return 429 quota exceeded", 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.