# Hyper Solutions API Documentation

## API Docs

- [Getting started](https://docs.hypersolutions.co/readme.md): Hyper Solutions generates sensor data for bypassing Akamai Bot Manager, Incapsula, DataDome, and Kasada.
- [SDKs & Examples](https://docs.hypersolutions.co/readme-1.md): We have SDKs for the following languages: Golang, Python, NodeJS/TS.
- [Usage Statistics](https://docs.hypersolutions.co/usage-statistics.md): Monitor your remaining quota and usage statistics with our simple Usage API endpoint.
- [Compression](https://docs.hypersolutions.co/compression.md): Our API supports multiple compression algorithms to improve performance and reduce bandwidth usage.
- [User Agents](https://docs.hypersolutions.co/user-agents.md): This page explains the supported user agent configurations and how to maintain them for optimal performance across all Hyper Solutions APIs.
- [IP](https://docs.hypersolutions.co/ip.md): The majority of our APIs require an IP address as input. This page explains how you can get the IP of your proxy.
- [Getting started](https://docs.hypersolutions.co/akamai-web/getting-started.md): This page explains the flow of generating sensor data and obtaining valid cookies for websites protected by Akamai Bot Manager.
- [SBSD Introduction](https://docs.hypersolutions.co/akamai-web/sbsd-introduction.md)
- [SBSD Challenge Flow](https://docs.hypersolutions.co/akamai-web/sbsd-challenge-flow.md)
- [Handling 429 Status Codes with SBSD Challenges](https://docs.hypersolutions.co/akamai-web/handling-429-status-codes-with-sbsd-challenges.md)
- [Handling 428 Status Code (SEC-CPT)](https://docs.hypersolutions.co/akamai-web/handling-428-status-code-sec-cpt.md)
- [Getting started](https://docs.hypersolutions.co/incapsula/getting-started.md)
- [Reese84](https://docs.hypersolutions.co/incapsula/reese84.md): Reese84 is a bot detection system by Imperva / Incapsula that runs a background script to generate a sensor and set a cookie, without displaying a challenge page.
- [Reese84 Dynamic](https://docs.hypersolutions.co/incapsula/reese84-dynamic.md): Reese84 Dynamic is used by sites that show a "Pardon Our Interruption" challenge page. Clients must solve the challenge and submit a valid payload to access the protected content.
- [Incapsula Captcha Block](https://docs.hypersolutions.co/incapsula/incapsula-captcha-block.md)
- [UTMVC](https://docs.hypersolutions.co/incapsula/utmvc.md)
- [Getting started](https://docs.hypersolutions.co/datadome/getting-started.md): This page explains the flow of solving both the interstitial and slider challenge of DataDome.
- [Tags](https://docs.hypersolutions.co/datadome/tags.md)
- [Slider (captcha)](https://docs.hypersolutions.co/datadome/slider-captcha.md): This page explains the flow of solving the slider challenge of DataDome.
- [Interstitial](https://docs.hypersolutions.co/datadome/interstitial.md): This page explains the flow of solving both the interstitial and slider challenge of DataDome.
- [Getting started](https://docs.hypersolutions.co/k4sada/getting-started.md): This page covers the different Kasada implementation flows you may encounter.
- [Flow 1: Initial Block Page](https://docs.hypersolutions.co/k4sada/flow-1-initial-block-page.md): This flow applies to websites like Hyatt.com where Kasada blocks you immediately when you first access the site with a 429 status code.
- [Flow 2: Fingerprint Endpoint](https://docs.hypersolutions.co/k4sada/flow-2-fingerprint-endpoint.md): This is the standard Kasada implementation where the browser makes a background request to the /fp (fingerprint) endpoint. This flow applies to most Kasada-protected websites.
- [Vercel BotID](https://docs.hypersolutions.co/k4sada/vercel-botid.md): This flow applies when a site is protected by Kasada through Vercel BotID.  You can identify this by the presence of the \`x-is-human\` header on requests  to protected endpoints.
- [Supported User Agents](https://docs.hypersolutions.co/k4sada/supported-user-agents.md): This page documents all user agent configurations supported by the Hyper Solutions Kasada API.
- [Authentication](https://docs.hypersolutions.co/api-reference/authentication.md): Authentication can be done in two ways.
- [Akamai](https://docs.hypersolutions.co/api-reference/akamai.md)
- [Incapsula](https://docs.hypersolutions.co/api-reference/incapsula.md)
- [DataDome](https://docs.hypersolutions.co/api-reference/datadome.md): This page shows the API Reference for our DataDome API.
- [Kasada](https://docs.hypersolutions.co/api-reference/kasada.md)
- [TLS Fingerprinting](https://docs.hypersolutions.co/request-based-basics/tls-fingerprinting.md): This page explains everything you need to know about TLS when making requests based modules.
- [Header Order](https://docs.hypersolutions.co/request-based-basics/header-order.md): This page explains everything you need to know about headers and header order when making requests based modules.
- [Installing Charles WebProxy](https://docs.hypersolutions.co/request-based-basics/installing-charles-webproxy.md)
- [Installing powhttp](https://docs.hypersolutions.co/request-based-basics/installing-powhttp.md)
- [Recording HAR files for Harvey](https://docs.hypersolutions.co/request-based-basics/recording-har-files-for-harvey.md): This page explains how to record HAR files from your code to receive support. We explain how to do this with the recommended tools: Charles Webproxy and PowHTTP.