Account/key: key ending in ...c49272 (also reproduced with a separate, previously-active key ending in ...b9d8d/7c62 before regenerating)
Issue: Requests to the transcript endpoint intermittently return 401 {"error":"unauthorized","details":"Invalid API Key: <correct key>"} even though:
• The dashboard confirms the key is active with unused credits (23/100 used at time of testing) • The exact same key succeeds on some requests and fails on others, with no change to the request • Confirmed using both raw HTTP requests and your official Python SDK (supadata package) • Reproduced across multiple video IDs and both the legacy (/v1/youtube/transcript?videoId=) and current (/v1/transcript?url=) endpoint formats
Reproduction pattern observed (2026-09-23, times approximate, UTC):
Request via Python SDK to /v1/transcript?url=https://youtu.be/CuqDCniCTTE → succeeded
Same exact call, same key, ~2 minutes later → failed, 401 Invalid API Key
Retried the identical request 3 more times over the following ~2 minutes → all failed, same error
This mirrors a separate, ~2-day period (Sept 21-23) where an earlier key on this same account was rejected on essentially every attempt (~10+ calls) via raw HTTP, before being regenerated
What this rules out: not a stale/incorrect key (verified byte-for-byte against dashboard), not a billing/quota issue (confirmed ample credits), not a client-side request formatting issue (reproduced identically via curl and your own official SDK), not a general network/Cloudflare block (other Cloudflare-fronted sites reachable fine from the same origin).
Ask: this looks like an intermittent issue in your auth-validation layer rejecting genuinely valid keys. Could someone look into what's causing keys shown as valid/active in the dashboard to be inconsistently rejected at the API layer? Happy to provide exact request timestamps/logs if useful for tracing this on your end
