Skip to content

Free, Open Source, Self-Hosted WhatsApp API Gateway

docs(devops): document the 429 on repeated bad metrics tokens

Yudhi Armyndharis04a27c224f1e
diff --git a/docs/10-devops-infrastructure.md b/docs/10-devops-infrastructure.md
index d0700b27c..c54a6f708 100644
--- a/docs/10-devops-infrastructure.md
+++ b/docs/10-devops-infrastructure.md
@@ -896,7 +896,9 @@ short TTL (~5s, so back-to-back scrapes don't repeat the DB scan), and exposes i
Access is **disabled by default**: the endpoint returns **404** unless `METRICS_TOKEN` is set. When
set, scrapers must send `Authorization: Bearer <token>` (compared with `timingSafeEqual`); a missing or
-wrong token returns 401. The token is **separate** from the API key — the route is `@Public()` (skips
+wrong token returns 401. After 10 failed attempts from one client IP within a minute, that client is
+answered 429 (even with the correct token) until the window slides; a successful scrape does not count
+against the limit. The token is **separate** from the API key — the route is `@Public()` (skips
the API-key guard) and `@SkipThrottle()`.
```typescript