Skip to main content
After purchasing a Layer 7 protection plan, you receive a custom API token that grants access to the management API at https://api.packets-decreaser.net/. Use this API to add domains, update configuration, and view clean traffic statistics. The steps below walk you through adding your first protected domain.

Setup steps

1

Retrieve your API token

Check your account dashboard or the email sent after purchase for your API token. You will include this token in the Authorization header of every API request.
2

Add your domain via the API

Send a POST request to https://api.packets-decreaser.net/domain with a JSON body containing your domain configuration. At minimum, provide domain and backend.
3

Create a CNAME DNS record

In your DNS provider’s control panel, add a CNAME record for your domain pointing to the Packets Decreaser filter node.
CNAME value: filter-l7.packets-decreaser.netSet the record for the root domain (e.g., example.com) or a subdomain you want to protect. DNS propagation typically takes a few minutes up to 48 hours depending on your provider and TTL settings.
4

Verify traffic is flowing

Once DNS propagates, visit your domain over HTTPS. Traffic will route through the Packets Decreaser edge. Check the clean traffic statistics endpoint to confirm requests are being recorded.

Domain configuration reference

Use these fields when adding or updating a domain via the API.

Core settings

string
required
Your domain name to protect (e.g., example.com).
string
required
The IP address and port of your backend server in IP:port format (e.g., 127.0.0.1:8082).
string[]
HTTP methods to allow through the proxy. Accepted values: GET, POST, PUT, PATCH, DELETE, HEAD, OPTIONS, CONNECT, TRACE.
boolean
default:"false"
Enable automatic SSL certificate provisioning. When enabled, you do not need to supply ssl_cert or ssl_key. Certificate issuance can take up to 30 minutes.
boolean
default:"false"
Enable SEO mode to allow verified search engine crawlers to bypass challenge stages.
string
An optional URL that Packets Decreaser calls when an attack is detected on this domain. Use this to trigger alerts or automated responses in your infrastructure.

Rate limiting

number
Maximum requests per second from a single IP per edge node before that IP is rate-limited at the edge.
number
Maximum short-term request burst per client IP per edge node before temporary throttling is applied.

Challenge stage thresholds

The filter layer applies up to three sequential challenge stages. These fields control when each stage activates or deactivates based on the global rate of requests bypassing the current stage.
number
Maximum global bypassing RPS in Stage 1 (Cookie Challenge) before the system escalates to Stage 2 (PoW JS Challenge).
number
Maximum global bypassing RPS in Stage 2 (PoW JS Challenge) before the system escalates to Stage 3 (Captcha).
number
Global request rate threshold at which Stage 2 (PoW JS Challenge) is deactivated and the system steps back to Stage 1.
number
Global request rate threshold at which Stage 3 (Captcha) is deactivated and the system steps back to Stage 2.
number
Number of seconds used to detect changing traffic behavior before issuing a JS challenge. Lower values make the system react faster to traffic spikes.

PoW difficulty

When Stage 2 (PoW JS Challenge) is active, the difficulty setting controls how computationally expensive the challenge is for the client. Higher difficulty blocks more sophisticated bots but adds latency for legitimate users.
Start with difficulty 4 for most sites. Increase to 5 or 6 only if you are seeing large volumes of bot traffic that passes difficulty 4.

Available API actions