Skip to main content
The Quickstart runs the Reese84 flow once. This page explains the parts, so you can recognize the variants, handle the puzzle, and keep a session going for hours rather than minutes.

How to recognize a Reese84 site

Any of these means the site runs Reese84:
  • A cookie named reese84 in a browser session.
  • A POST in your powhttp recording to a URL ending in ?d=<host> with a JSON body and a JSON reply containing token.
  • On some sites, API requests carrying an x-d-token header with the same value as the cookie.
The sensor script lives at a fixed but random-looking path on the site’s own host. The submission goes to the same URL with ?d=<host> appended.

Two variants

The flow is identical either way. The Quickstart’s script finder handles both shapes, and the GPC probe returns an empty string on sites that do not use it, so one implementation covers both.

The GPC puzzle

Sites can require a small proof of work before they accept a submission. The browser asks for it by posting {"f":"gpc"} to the script URL with ?d=<page host>. The reply is a JSON string: empty when there is no puzzle, otherwise a base64 envelope containing a 16-byte seed and a SHA-1 target. Pass that string to Roolink as pow, exactly as received. Roolink solves it while building the submission and includes the proof where the site expects it. Do not decode or solve it yourself; a pre-solved proof is not accepted. The solve is bounded at ten seconds, and a puzzle that runs past it returns 504; retry once.

The token

The submission reply is JSON with three fields you use: On sites whose API calls carry x-d-token, send the same token in that header too. Your recording shows which requests need it.

Renewing

A token is a session, not a one-off. To keep it alive, repeat the fetch-build-submit cycle in the same session before renewInSec elapses, and replace the cookie with the new token. Renewal does not need a fresh page load: the script URL is stable per site, so cache it, fetch the script again to pick up any change, probe GPC, build, submit. Roolink’s /payload response carries an old_token field for compatibility with the browser’s submission shape; you do not need to fill it in. Roolink builds the Reese84 submission from a real browser that visited a site recently and sent the same User-Agent you pass in userAgent, and takes the languages and time zone from language. Send a current desktop Chrome User-Agent from Windows or macOS, with matching client hints and the newest Chrome TLS profile your client offers. A User-Agent no collected browser has, such as an old Chrome version or Linux, gets 422 device_not_found. The Supported browsers page has the details.

Request fields

Troubleshooting

The IP changed mid-session, or the User-Agent differs between the page load and the submission. Both invalidate the token early.
On dynamic sites, confirm the GPC probe returned a puzzle and that you passed it to Roolink. A submission built without the proof is refused, and the site shows the interstitial again.