Skip to main content
Roolink is one API key and, today, two products. This page covers the part that is the same for all of them, then sends you to the quickstart for the product protecting your target.

​
Get your API key

Create an account, choose a plan, and copy the key from the dashboard. Every request to Roolink carries it in an x-api-key header. Send it only to *.roolink.io, never to a target site.

​
Install the tools

You need two libraries and one desktop tool. The Roolink SDK talks to Roolink. A TLS client talks to the target site: bot protection fingerprints the connection itself before it reads anything you send, so an ordinary HTTP library is refused on the first request. These connect the way Chrome does; Set up your HTTP client shows the full configuration. powhttp is the tool. It records what Chrome really sends, header order included, and what your script sends, so you can copy the first and check the second. Download it from powhttp.com; it is free and runs on Windows, macOS and Linux. Keep the key and a proxy URL in environment variables. The proxy must keep one IP for the whole session, because bot protection ties its cookies to the IP.

​
Pick your product

Each quickstart ends with a solved challenge on a real site. Not sure which protection you are facing? Identify it in two minutes.

Akamai Web

Websites behind Akamai Bot Manager. Look for _abck and bm_sz cookies.

Quickstart

Akamai BMP

iOS and Android apps behind Bot Manager Premier.

Quickstart