Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.hackgate.io/llms.txt

Use this file to discover all available pages before exploring further.

Rate limiting prevents researchers from sending excessive traffic that could degrade your application during testing. Assign a named rate limiter policy to any HackGATE to enforce request-rate boundaries.

​
Set a rate limit

Assign a rate limiter policy to a site by name: 
curl -X POST https://admin.hackgate.io/api/sites/setRateLimiting \
  -H "Authorization: Bearer <your-token>" \
  -H "Content-Type: application/json" \
  -d '{"id": "<site-id>", "rateLimit": "fixed"}'
The response returns the updated site object with rateLimit set to the policy name you provided.

​
Available policies

Policy nameBehavior
fixedFixed window rate limiter — limits requests within a fixed time window.
slidingSliding window rate limiter — smooths out traffic over a rolling window.
Contact support@hckrt.com if you need a custom rate limiter policy configured for your organization.

​
Remove a rate limit

Set rateLimit to an empty string to remove rate limiting from a site: 
curl -X POST https://admin.hackgate.io/api/sites/setRateLimiting \
  -H "Authorization: Bearer <your-token>" \
  -H "Content-Type: application/json" \
  -d '{"id": "<site-id>", "rateLimit": ""}'
Rate limiting applies across all researchers accessing the HackGATE, not per individual researcher.
Last modified on May 9, 2026