🎯 Goal
Obtain Rewards Codes for 20–30 Three+ accounts, simulating user actions through HTTP requests.
Authorization — via valid cookies / session tokens, without login and password.
⚙️ Functionality
✅ Program runs manually on Windows (no auto-start, no background services)
✅ Processes 20 accounts per run (value edited via config)
✅ Works through HTTP requests, without browser, without Selenium, without WebDriver
✅ Uses cookies / session (CSV or JSON, provided by me)
✅ Emulates real User-Agent + headers, introduces delays 2–5 minutes (random) for realistic behavior
🔄 Algorithm
Go to the Cineworld section
Emulate clicking Get Rewards (POST or required request).
If the code does not appear immediately — go to My Codes and retrieve it there
Save the obtained code in CSV (format: login + code, cookies)
✅ After processing 20 accounts, the program terminates
✅ All parameters (path to CSV, Rewards URL, delays, etc.) — via settings.json or .ini
✅ The program does not perform re-login, uses existing cookies
✅ Do not change IP, do not use proxies
🗺️ Site Features
Domain: https://threeplus.three.co.uk
Rewards URL changes every Monday (should be configurable in settings)
Site built on Flutter Web (canvas), HSTS active, No Captcha
🛠️ Technologies
✅ Python
✅ requests or httpx
✅ random + time.sleep
✅ Config via JSON or INI
📦 What I provide
🗂️ CSV file with account list
🔐 Cookies or session tokens
🎥 Video tutorial on how to manually obtain codes
🧠 Additional information:
🖼️ Site built on Flutter Web, uses canvas and has HSTS protection.
🔣 Codes — simple numbers, visible after login.
🧩 No captcha or complex checks on the site when working manually.
📝 Waiting for release
✅ .exe
✅ Full source code with comments
✅ README or setup instructions
✅ Example configuration file (for inserting cookies/tokens and changing URL)
🚨 Important
🧍♂️ All actions must imitate manual user work.
The program should operate as "human-like" as possible (with pauses, real User-Agent, and without sudden simultaneous requests), to avoid blocks or SMS verification requests.
✅ Manual site operation is stable — in 20 minutes I can easily obtain codes from 40 accounts.
✅ The program should repeat this exact speed (not faster, not slower) to avoid suspicion.
✅ When placing bets: Please briefly describe how you see the implementation of this project
