Exchange API key banned after bot deploy
Automation appears healthy, then keys are throttled or blocked with little warning. Typical causes are bursty startup behavior, weak limiter coordination, and policy drift across instances.
Common symptom variants
Primary playbook
When API key flips from working to 403 forbidden after bot runs for hours: why exchange APIs ban trading bots for traffic bursts, retry storms, and auth failures, and the client behavior that prevents it.
Recommended resource
Two files: an API key permissions checklist plus retry/backoff safe defaults for exchange clients. Download includes both markdown files.
Related posts
Trading bot keeps getting 429s after deploy: stop rate limit storms
When deploys trigger 429 storms: why synchronized restarts amplify rate limits, how to diagnose fixed window vs leaky bucket, and guardrails that stop repeat incidents.
Signature invalid but bot was working: why clock drift breaks auth suddenly
When bot gets signature invalid or 401 after working fine for hours: why clock drift breaks exchange auth suddenly, and the time calibration that prevents it.