Slingshot Sniper

Session / Cookies

The Walmart cookie jar + residential proxy the in-process fire uses (replaces sniper-py's local cookies.txt). When a queue is detected the server fires issueTicket with this session if NODE_FIRE_ENABLED is on.

Cookie header — paste from DevTools → Network → q-api request → Request Headers → cookie (HttpOnly cookies are not in document.cookie)

Residential proxy (user:pass@host:port) — fire routes through this; IP must match the redeem browser

Per-product proxies

One fire proxy per product (mirrors sniper-py's per-item proxy). Products are added under Relay → Monitored Items; set each one's fire proxy here. An item with no proxy falls back to the default proxy in Session / Cookies above. Each ticket binds to its fire IP, so spreading products across IPs is what lets you redeem several at once.

Preflight — validate before a drop

Benign validateTickets GET through the stored jar + proxy (no side effects) plus a TLS fingerprint echo. Run until q-api shows 200 PASSED and the JA4 / H2 hashes match sniper-py before flipping NODE_FIRE_ENABLED=1.

Slingshot

Slingshot

Session / Cookies

Per-product proxies Refresh

Preflight — validate before a drop

Per-product proxies