# HttpProtectOptions.maxRequests property · @imqueue/http-protect

Source: https://imqueue.org/api/http-protect/latest/http-protect.httpprotectoptions.maxrequests/
Published: 2026-08-01
Author: @imqueue maintainers (https://github.com/imqueue)
Package: @imqueue/http-protect 3.0.1 — generated reference, not hand-written

Requests an address may accumulate before it is answered 429.

**Signature:**

```typescript
maxRequests?: number;
```

## Default Value

`200`

## Remarks

Exceeding it yields [VerificationStatus.LIMITED](https://imqueue.org/api/http-protect/latest/http-protect.verificationstatus/) and HTTP 429, and the address recovers by going quiet for [HttpProtectOptions.ttl](https://imqueue.org/api/http-protect/latest/http-protect.httpprotectoptions.ttl/) seconds — this threshold carries no lasting consequence on its own.

Choose the value against a continuous stream rather than a rate, because that is what the counter measures (see [HttpProtectOptions.ttl](https://imqueue.org/api/http-protect/latest/http-protect.httpprotectoptions.ttl/)). At the defaults, 200 requests inside 10 seconds trips it, and so does one request per second for 200 seconds — the second of which is ordinary behaviour for a real user on a busy page. Raise it, or raise `ttl` and this together, if legitimate sessions are long-lived.

Also settable as `HTTP_PROTECT_MAX_REQUESTS`; a value passed here wins.