Complete, working examples for bypassing modern bot protection systems using the Hyper Solutions SDK.
| Protection | Description |
|---|---|
| Akamai Bot Manager | Sensor data generation, SBSD challenges, cookie validation |
| DataDome | Interstitial challenges, slider captcha, tags/signal collection |
| Incapsula (Imperva) | Reese84 sensor generation, POW challenges |
| Kasada | Payload generation (CT), POW tokens (CD), BotID verification |
├── golang/
│ ├── akamai/
│ │ ├── azuretls/
│ │ └── bogdanfinn/
│ ├── datadome/
│ │ ├── azuretls/
│ │ └── bogdanfinn/
│ ├── incapsula/
│ │ ├── azuretls/
│ │ └── bogdanfinn/
│ └── kasada/
│ ├── azuretls/
│ └── bogdanfinn/
│
├── node/
│ ├── akamai/
│ │ └── tlsclientwrapper/
│ ├── datadome/
│ │ └── tlsclientwrapper/
│ ├── incapsula/
│ │ └── tlsclientwrapper/
│ └── kasada/
│ └── tlsclientwrapper/
│
└── python/
├── akamai/
│ ├── rnet/
│ └── tls-client/
├── datadome/
│ ├── rnet/
│ └── tls-client/
├── incapsula/
│ ├── rnet/
│ └── tls-client/
└── kasada/
├── rnet/
└── tls-client/
Sign up at hypersolutions.co to get your API key.
export HYPER_API_KEY="your-api-key-here"Go (bogdanfinn/tls-client)
cd golang/kasada/bogdanfinn
go mod tidy
go run main.goNode.js (tlsclientwrapper)
cd node/kasada/tlsclientwrapper
npm install
node index.jsPython (tls-client, synchronous)
cd python/kasada/tls-client
pip install -r requirements.txt
python main.pyPython (rnet, asynchronous)
cd python/kasada/rnet
pip install -r requirements.txt
python main.py| Library | Description |
|---|---|
| bogdanfinn/tls-client | TLS client with browser fingerprint support |
| Noooste/azuretls-client | Alternative TLS client with Chrome fingerprinting |
| Hyper-Solutions/hyper-sdk-go | Hyper Solutions Go SDK |
| Library | Description |
|---|---|
| tlsclientwrapper | TLS client wrapper using Koffi bindings and worker pools |
| hyper-sdk-js | Hyper Solutions JavaScript/TypeScript SDK |
| Library | Description |
|---|---|
| rnet | Async TLS client with browser emulation (Rust-powered) |
| Python-Tls-Client | TLS client with browser impersonation |
| hyper-sdk | Hyper Solutions Python SDK |
Each example includes a configuration object with the following common options:
| Option | Description |
|---|---|
api_key / apiKey |
Your Hyper Solutions API key |
target_url / targetUrl / page_url / pageUrl |
The protected page URL |
proxy_url / proxyUrl |
Optional HTTP/HTTPS/SOCKS5 proxy |
accept_language / acceptLanguage |
Browser accept-language header |
timeout |
Request timeout duration |
Protection-specific options are documented in each example file.
- Fetch target page and detect protection (SBSD or sensor)
- If SBSD detected: fetch script, generate payload, POST
- Parse sensor endpoint from page
- Fetch sensor script
- Generate and POST sensor data (up to 3 times)
- Validate
_abckcookie
- Fetch target page to trigger DataDome
- Detect challenge type (interstitial vs slider)
- If interstitial: fetch page, generate payload, POST
- If slider: fetch captcha, download images, solve, submit
- Optional: send tags requests for signal collection
- Verify access
- Fetch target page to trigger challenge
- Extract script paths from challenge page
- Fetch Reese84 script
- Optional: get POW challenge
- Generate sensor via API
- POST sensor to get token
- Set
reese84cookie and verify access
- Fetch target page or
/fpendpoint - Detect 429 response and extract
ips.jsURL - Fetch ips.js script
- Generate payload via API
- POST payload to
/tlendpoint - Optional: solve BotID challenge
- Generate POW (x-kpsdk-cd) for protected requests
All examples use Chrome 143 fingerprints:
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/143.0.0.0 Safari/537.36
sec-ch-ua: "Google Chrome";v="143", "Chromium";v="143", "Not A(Brand";v="24"
sec-ch-ua-platform: "Windows"
TLS fingerprints are configured to match Chrome 133 profile for consistency with the TLS client libraries.
- Header order matters. All examples carefully maintain HTTP header order to match real browser behavior.
- Cookie handling. Examples use proper cookie jar management for session persistence.
- IP consistency. Your public IP is sent to the API for fingerprint consistency. Use the same proxy for all requests.
- Node.js requirements. The tlsclientwrapper requires Node.js 16+ and a platform supported by Koffi (Windows, macOS, Linux).
MIT License. See LICENSE for details.