-
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.
Trade requests impersonate a real browser, and cf_clearance only works together with the exact browser that issued it. Google Chrome or Firefox must be installed — pick one in the Browser selector at the top of the Trade Cookies section and always copy the cookies from that same browser on this PC. POE2Fixer automatically matches its trade identity to the installed version of the selected browser (cookies from any other browser, e.g. Edge, will not pass the trade-site check).
-
Install Google Chrome or Firefox and select the same browser in the Browser selector.
-
Open
https://www.pathofexile.com/trade2/in that browser and log in. Complete the Cloudflare check if it appears. -
Press F12 to open DevTools → Application tab (Chrome) 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, then press Check cookies.
The Check cookies button loads the trade site with your cookies and checks whether a POETOKEN is issued:
- POETOKEN received — the cookies fully pass the trade-site check; you're good to go.
- POETOKEN not received — you can still continue (the token is optional and trading works without it), but if trading misbehaves, paste fresh cookies from the selected browser and check again.
-
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.
- 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.