Tasks

This section explains how to set up and customize your Fastix tasks — the core of how the bot interacts with events.

Now we will configure the tasks.csv that you can find here.

Normal mode

Before starting a task in Fastix Bot, you’ll need to set up a few parameters that tell the bot what event to run and how to behave.

  • Task_ID – Enter any custom name to help you identify the task or event you’re running.

  • Event_URL – Paste the full URL of the event you want Fastix to monitor or purchase from.

  • Service – Keep this set to "ticketmaster" for now. More platforms (like AXS) will be supported soon.

  • Mode – Choose between:

    • atc – Queues your accounts and automatically carts tickets once passed.

    • queue – Queues accounts only (you’ll cart manually).

    • resale – Purchases resale tickets automatically.

    • pw_reset – Update password of the accounts.

  • Presale_code – Use this option to enter the presale codes for the event you’re running. You can either type the codes directly into the field, or upload a .txt file containing them — one code per line, like this:

    Fastix will automatically read and use all the codes from that file.

💡 Example: If you name your file codes.txt, make sure it’s in the same folder as your config. Then, in the presale_code field, simply enter the exact filename on this case codes.txt

Ticket Settings

Fine-tune how many tickets Fastix should target and under what conditions.

  • Use_Proxy – Set to true to route traffic through proxies, or false to run without them.

  • Number_of_Tickets – Minimum number of tickets to auto-cart (only used in ATC mode).

  • Max_Tickets – Maximum number of tickets allowed in the cart.

  • Min_Price – Minimum price per ticket to target.

  • Max_Price – Maximum price per ticket to target.

  • Include_Resale – Set to true to include resale tickets, or false to exclude them.

  • Ticket_Type_Priority – Define your ticket preference:

    • seated for reserved seats

    • standing for general admission

    • seated,standing will try to cart first seated and then standing and if you put standing,seated will try to cart first standing and then seated.

Account & Proxy Details

Add your account information and connection details for Ticketmaster.

  • Delay_Between_Accounts – Delay (in seconds) between task starts for multiple accounts.

  • First_Name – First name on your Ticketmaster account.

  • Last_Name – Last name on your Ticketmaster account.

  • Email – The email address linked to your Ticketmaster account.

  • Password – Account password.

  • Postal_Code – ZIP or postal code registered on your account.

  • Phone_Number – Your Ticketmaster account phone number with the prefix.

  • Proxy – (Optional) Assign a specific proxy to this account for better performance or region targeting.

  • Wait_queue - Set to true will wait queue to start and do the presave of the otp, or false . (Run 30 minutes before the queue starts, really recommend it)

  • Imap email: Copy your master email — the one where all your emails are forwarded. Example: [email protected]

  • Imap password: Copy the IMAP password of your master email account. This will be used by the bot to log in and check for verification emails.

  • Imap_server: The server that lets your email app sync and access messages stored online.

    • iCloud IMAP: imap.mail.me.com

    • Gmail IMAP: imap.gmail.com

  • Section targeting: lets you specify which seat sections to target directly in your CSV task file (503,101,GA). You can use simple text keywords or more advanced Regex patterns by wrapping them in slashes (e.g., /W1.*/).

Account generator mode

The Account Generator allows you to automatically create accounts using your provided email addresses. Before running it, make sure all the required parameters are correctly filled in.

First of all, you will need to install this file.

How it works

In this mode, you just need to enter your list of emails that will be used for creating accounts, along with the IMAP credentials of your master email. The bot will use that IMAP connection to verify and confirm account creations automatically.

🔹 Parameters

  • Email: Copy all the email addresses you want to use to create accounts. Each address should be written on a separate line (for example: [email protected]).

  • Imap email: Copy your master email — the one where all your emails are forwarded. Example: [email protected]

  • Imap password: Copy the IMAP password of your master email account. This will be used by the bot to log in and check for verification emails.

🔹 Results

After the generation process is complete:

  • All successfully created accounts will be confirmed automatically using the verification emails found in your master mailbox.

  • If some accounts fail to verify, their information will be stored in a separate log file so you can review or retry them later.

🔹 Tips

  • Make sure IMAP access is enabled on your master email account.

  • If you’re using Gmail or Outlook, you may need to use an App Password instead of your main login password.

  • Never share your IMAP credentials publicly.

  • Keep your email list clean and formatted correctly to avoid creation errors.

Proxy checker mode

The Proxy Checker Mode allows you to test your proxies directly within the bot to ensure they are working correctly before using them for real tasks.

🔹 How it works

In this mode, you just need to select the proxies you want to test on the bot, and choose a task with a valid event to use for testing those proxies. The bot will automatically run a quick connection check for each proxy and determine whether it’s working or not.

🔹 Results

After the test is complete:

  • All working proxies will be automatically saved in the fastix folder. Inside that folder, you’ll find a file named working_proxies.txt, which contains the list of all proxies that passed the test.

  • The proxies that failed the test will remain logged inside the file proxy_test_metrics.txt, so you can review their performance or errors later.

🔹 Tips

  • Make sure your proxies are correctly formatted before running the test.

  • You can recheck failed proxies from the proxy_test_metrics.txt file to identify possible network or authentication issues.

  • Use the working_proxies.txt file in other modes of the bot for better performance and reliability.

Signup mode

The Signup Mode allows you to automatically sign up for a selected event using your Ticketmaster account credentials.

Download this file

🔹 How it works

In this mode, you need to provide all the required parameters for the bot to complete the signup automatically. It will log into your Ticketmaster account, access the event signup page, and register you for the selected date.

🔹 Parameters

  • Signup: Paste the URL of the signup event. Example: https://signup.ticketmaster.com.mx/rush

  • Email: Paste the email of your Ticketmaster account.

  • Password: Paste the password of your Ticketmaster account.

  • Selection: Choose the date number you want to sign up for.

    • 0 → first day

    • 1 → second day

    • 2 → third day, and so on.

  • Proxy (optional): You can select your proxies.txt file if you want the bot to use proxies during the signup. If you don’t select any, the signup will proceed using your default connection.

🔹 Results

After the signup is completed:

  • The bot will confirm if your signup was successful.

  • Any errors or failed attempts will be logged automatically, so you can check what went wrong.

🔹 Tips

  • Always make sure the signup URL is correct and active.

  • Check that your Ticketmaster account credentials are valid and not blocked by 2FA.

  • Using proxies is recommended when handling multiple signups or accounts.

  • Review your log files after each run to ensure all signups were processed correctly.

Monitor Guide

Monitor Mode allows you to automatically track stock for specific events and instantly alert your accounts when new tickets appear. It’s designed to run continuously in the background, scanning Ticketmaster events and triggering checkouts the moment stock is detected.

⚙️ How It Works

  1. Add your accounts in accounts.csv (you can use just one if you prefer).

  2. Each monitor will continuously check the event URL(s) you’ve added in your monitors.csv

  3. When stock is found, all linked accounts will be pinged automatically to attempt checkout.

  4. Running multiple monitors on the same event increases your chances of being the first to detect stock.

💡 Example: If you’re monitoring multiple regions or drops, you can run one monitor per event link to cover more ground.

🗂️ CSV Parameters

Parameter
Description

event_url

The full URL of the event you want to monitor.

polling_interval

Defines how often Fastix checks for stock. You can use a fixed number (e.g. 5) or a random range (e.g. 4-6).

numberOfTickets

Number of tickets to cart when stock is found.

maxNumberOfTickets

Maximum number of tickets to allow in the cart.

priceRange_enabled

Set to true to activate price filters.

priceRange_min / max

Define the minimum and maximum price for tickets.

includeResale

Set true to include resale tickets in the scan, false to skip them.

ticketTypePriority

Choose seated, standing, or a combination (e.g. seated,standing). The order defines the priority — for example, seated,standing will try seated first, then standing if none are available.

selectionStrategy

Strategy used to select tickets (e.g. cheapest_in_range or max_available).

⏱️ Polling Interval Explained

The polling_interval controls how often the bot checks for new stock.

  • 5 → checks every 5 seconds exactly.

  • 4-6 → checks every 4 to 6 seconds randomly.

💡 Tip: Use a small random range (4-6, 5-7) to stay fast and realistic.

AXS Guide

Running AXS events with Fastix is super simple it uses the same CSV format as Ticketmaster. Just follow these quick steps and you’ll be ready for the queue.

Task Setup

  1. CSV File: Use the same CSV file format as for Ticketmaster tasks no need to change anything.

  2. Event Link: Paste the AXS queue link directly in the event_url field.

  3. Mode: Set the mode to queue

  4. Use Proxy: Always set true this helps avoid IP-based rate limits.

  5. Wait Queue: Always set this option on true for AXS

  6. Service: When prompted by the bot, choose axs

Notes

  • Fastix doesn’t use your accounts, ticket types, or any other parameters for AXS — only the event link and proxy setup matter.

  • Once configured, just run your task and let Fastix handle the rest when the queue opens.

  • For AXS the only provider that works is Capmonster.

PreviousFirsts stepsNextTypical Errors

Last updated