Automated Ticket Buying Desktop App
Budget / Salary$750–1,500
TypeFreelance project
LocationRemote
Posted1 hour ago
I’m seeking an experienced developer to complete an existing automated ticket-buying bot with a Windows desktop dashboard for Ticketmaster and SeatGeek. The developer must have already done numerous projects related to this and is skilled at anti-bot resilience. Such as fingerprint spoofing, residential proxy rotation, and CAPTCHA solving hooks. You must have extensive experience bypassing strict anti-bot protections such as, (DataDome, Cloudflare, Akamai).
The main deliverable is a working purchasing engine that automatically monitors ticket availability, identifies tickets matching my criteria, reserves them, and completes checkout using assigned accounts and supported saved payment methods. The dashboard must let me configure and monitor this automation without editing code.
Source files, executables, screenshots, and an improved dashboard with simulated workflows are available. The existing simulation does not fulfill the automatic purchasing requirement.
Automatic Purchasing Requirements
Once I configure and start a task, the bot should automatically:
1. Open the specified event using the assigned account sessions.
2. Handle supported queue workflows and begin monitoring when access becomes available.
3. Identify inventory matching my section, row, ticket-type, quantity, seating, and price requirements.
4. Reserve qualifying tickets.
5. Verify the selected tickets, final quantity, and total price, including applicable fees and taxes.
6. Complete checkout through a supported, authorized integration using the assigned purchasing profile and payment method.
7. Verify the order outcome and record the confirmation details.
8. Notify me of successful purchases, failures, or required intervention.
9. Stop when the shared ticket target or spending limit is reached.
Provide two selectable operating modes:
- Automatic Purchase: Starting the task authorizes purchases within its configured event, ticket criteria, quantity, and spending limits. No additional approval is required for each qualifying purchase.
- Approval Required: Reserve qualifying tickets and request approval locally or through Discord before completing checkout.
Any authentication, verification, or payment step that requires human involvement must be clearly identified before development. The bot must pause and notify me when intervention is required.
Multiple Accounts and Purchase Controls
A single task must support multiple accounts and individual purchasing profiles, with an initial configuration target of 50 accounts. This will be more.
Coordinate activity across accounts so the bot does not purchase duplicate inventory or exceed shared limits. An individual account failure should not stop other eligible accounts.
After a timeout or uncertain checkout response, verify whether an order succeeded before retrying. Once the task target is reached, stop outstanding purchase attempts safely.
Required Live Demonstration
Demonstrate the complete automatic workflow separately on each supported platform: matching inventory, reservation, final-price validation, checkout submission, and verified order confirmation.
Use an agreed test environment or an explicitly authorized live purchase with a fixed spending limit.
Clearly identify unsupported features and unavoidable manual steps. A simulation, cart-only demonstration, or checkout link does not satisfy the automatic purchasing requirement.
Deliver and demonstrate the agreed live purchasing workflow on Ticketmaster and SeatGeek, including automatic checkout, verified order outcomes, coordinated account activity, enforced quantity/spending limits, duplicate prevention, and notifications. Acceptance requires evidence of the agreed end-to-end functionality on each platform.
The main deliverable is a working purchasing engine that automatically monitors ticket availability, identifies tickets matching my criteria, reserves them, and completes checkout using assigned accounts and supported saved payment methods. The dashboard must let me configure and monitor this automation without editing code.
Source files, executables, screenshots, and an improved dashboard with simulated workflows are available. The existing simulation does not fulfill the automatic purchasing requirement.
Automatic Purchasing Requirements
Once I configure and start a task, the bot should automatically:
1. Open the specified event using the assigned account sessions.
2. Handle supported queue workflows and begin monitoring when access becomes available.
3. Identify inventory matching my section, row, ticket-type, quantity, seating, and price requirements.
4. Reserve qualifying tickets.
5. Verify the selected tickets, final quantity, and total price, including applicable fees and taxes.
6. Complete checkout through a supported, authorized integration using the assigned purchasing profile and payment method.
7. Verify the order outcome and record the confirmation details.
8. Notify me of successful purchases, failures, or required intervention.
9. Stop when the shared ticket target or spending limit is reached.
Provide two selectable operating modes:
- Automatic Purchase: Starting the task authorizes purchases within its configured event, ticket criteria, quantity, and spending limits. No additional approval is required for each qualifying purchase.
- Approval Required: Reserve qualifying tickets and request approval locally or through Discord before completing checkout.
Any authentication, verification, or payment step that requires human involvement must be clearly identified before development. The bot must pause and notify me when intervention is required.
Multiple Accounts and Purchase Controls
A single task must support multiple accounts and individual purchasing profiles, with an initial configuration target of 50 accounts. This will be more.
Coordinate activity across accounts so the bot does not purchase duplicate inventory or exceed shared limits. An individual account failure should not stop other eligible accounts.
After a timeout or uncertain checkout response, verify whether an order succeeded before retrying. Once the task target is reached, stop outstanding purchase attempts safely.
Required Live Demonstration
Demonstrate the complete automatic workflow separately on each supported platform: matching inventory, reservation, final-price validation, checkout submission, and verified order confirmation.
Use an agreed test environment or an explicitly authorized live purchase with a fixed spending limit.
Clearly identify unsupported features and unavoidable manual steps. A simulation, cart-only demonstration, or checkout link does not satisfy the automatic purchasing requirement.
Deliver and demonstrate the agreed live purchasing workflow on Ticketmaster and SeatGeek, including automatic checkout, verified order outcomes, coordinated account activity, enforced quantity/spending limits, duplicate prevention, and notifications. Acceptance requires evidence of the agreed end-to-end functionality on each platform.
Apply on Freelancer →
Project sourced from Freelancer.com. Applications happen directly on the original platform — we never collect your data.