-
Notifications
You must be signed in to change notification settings - Fork 0
Trade Cookies
POE2Fixer needs two cookies from your pathofexile.com browser session to make trade requests on your behalf:
-
POESESSID— your logged-in session token. -
cf_clearance— Cloudflare anti-bot clearance cookie.
These are entered manually in Configuration → Settings → Trade Cookies. The values are encrypted at rest (Windows DPAPI, machine-bound) and held in memory inside a SecureString that scrubs itself on app exit.
-
Open
https://www.pathofexile.comin your regular browser (Chrome, Edge, or Firefox) and log in. Complete the Cloudflare check if it appears. -
Press F12 to open DevTools.
-
Go to the Application tab (Chrome / Edge) or Storage tab (Firefox) → Cookies → select
pathofexile.com. -
Find the
POESESSIDrow, double-click its Value, press Ctrl+C.(Screenshot: DevTools showing POESESSID highlighted)
-
In POE2Fixer, click the 📋 Paste button next to POESESSID in Settings.
-
Repeat for
cf_clearance.
-
POESESSIDexpires when you log out of pathofexile.com in your browser, or after a few weeks of inactivity. If trade stops working with HTTP 401, refresh both cookies. -
cf_clearanceexpires after ~1 hour of being unused, or whenever Cloudflare decides to re-challenge you. If trade returns HTTP 403, refreshcf_clearance.
Previous versions used an embedded Microsoft Edge WebView2 to scrape these cookies automatically. That added ~250 MB of runtime, depended on a separately-installed WebView2 Runtime, and complicated anti-cheat compatibility. Manual entry is a one-time setup; the values are stored encrypted and never leave your machine.
- Stored as a single DPAPI blob:
Configs/general/cookies.dat. The file is unreadable on any other machine. - The
config.jsonfile does not contain cookies (they're separate to avoid leaking via plaintext config). - The Settings UI does not allow copying values back out — the masked display uses an uncopyable label, not a text input. The reveal button shows the value in-place for verification only.