Ticketmaster

Ticketmaster task creation guide

To activate ACO mode, you need to fill in the profiles.csv file. - ProfileName - CcNumber - CcExpiryMonth - CcExpiryYear - CcCVV. And put the name of your ProfileName in your tasks.csv.

Tasks.csv

  • Mode (required) : The mode used by the task SALE , RESALE , SALE QUEUE , RESALE QUEUE, SALE MONITOR or IGNORE

SALE mode is the most common mode.

  • Mail (required ACO): The mail of your account.

  • Password (required ACO) : Your password from your account.

  • EventName (required) : This will be for you to identify which task is running

(eg : CLARA LUCIANI)

  • EventLink (required) : The event link used by the task

(eg :https://www.ticketmaster.fr/fr/manifestation/clara-luciani-billet/idmanif/580977)

Accor Arena links also work (eg : https://billetterie.accorarena.com/fr/manifestation/xmas-vybe-billet/idmanif/570076)

  • Delay (required) : It's the time duration in milliseconds a task will wait before each attempt to check stock. Must be equal or above 0 (eg : 2000)

  • Code (optional) : Only necessary if event is protected by a code (Usually required for presale).

  • DatesFilter (optional) : This is needed if an event has multiple dates and you only want to target specific dates on this event

(eg : 2025-02-22 or 2025-02-19;2025-02-20;2025-02-21 )

DATE FORMAT : YYYY-MM-DD

  • QuantitiesFilter (required) : The different quantities you want to target on a task.

(eg : 1;2;3;4 Here the bot will only target solo, duo, trio and quartor on the task) (eg : 2;3 Here the bot will only target duo and trio on the task) (eg : 2 Here the bot will only target duo on the task)

  • CategoriesFilter (optional) : The categories you want to target on a task.

(eg : PELOUSE Here the bot will only target PELOUSE category on the task) (eg : CARRE OR;FOSSE Here the bot will only target CARRE OR and FOSSE category on the task.) (eg : CARRE OR;FOSSE;CATEGORIE 1 Here the bot will target CARRE OR Category, FOSSE category and CATEGORIE 1 category on the task)

WARNING : If you don't know the exact name of the categories on an event let the column empty, we only suggest to use this column if you have the exact name of the categories on an event, otherwise use MinPriceFilter and MaxPriceFilter columns to target specific categories.

  • MinPriceFilter (optional) : The bot will target all the categories equal or above the given price.

(eg : 100 Here the bot will focus all the categories with ticket price above 100 euros)

  • MaxPriceFilter (optional) : The bot will target all the categories equal or below the given price.

(eg : 1000 Here the bot will focus all the categories with ticket price below 1000 euros)

  • CartNumber (optional and only used on SALE) : The number of carts attempts the bot will do on the task when it detects stock.

(eg : 5 Here the bot will do 5 cart attempts when he will detect stock on a category).

WARNING : If you let this column empty it will automatically set up 1 cart number.

  • CartLimit (optional) : This is the number of cart a task will do before stopping

(eg : 10 Here the bot will do 10 cart on the task, then this task will stop automatically)

  • CaptchaNumber (optional and only used on SALE) : Choose a number of pre-solved captchas that the task will use to cart.

  • CaptchaAPIKey (required) : Your Capsolver key. Will be used by the bot to solve captchas.

  • CookieName (optional) : The name of the Queue-it cookie associated with the event. If you don't have any tasks passing with the normal queue handling, and your cookgroup or a friend sent you a working cookie, you can input it here to use their queue pass.

Usually starting by "QueueITAccepted" like in the screen below (eg : QueueITAccepted-SDFrts345E-V3_valorantid100712 )

  • CookieValue (optional) : The value of the Queue-it cookie associated with the event. If you don't have any tasks passing with the normal queue handling, and your cookgroup or a friend sent you a working cookie, you can input it here to use their queue pass.

(Usually starting by "EventId%3D") (eg : EventId%3Dvalorantid100712%26Re.....)

You can also directly use a queue pass link. It works exactly the same as the Queue-it cookie value but you don't have to input something in CookieName column.

(eg: https://www.ticketmaster.fr/fr/manifestation/clara-luciani-billet/idmanif/580977?joinwaitinglist=true&queueittoken=e_s33generaltm~ts_1755356809~ce_true~q_7288d37c-425a-4318-b8db-08a35008bb16~rt_queue~ti_29f15ce5-2664-4f12-a39c-872b0ccbd9f4~h_428f4512c087350720329001a7235b517935988c384988eca6e1565a1e3dc367)

Cookie Injecting Methods

There are two methods to inject cookie with tasks.csv:

  1. By using a queue pass link (You will need to fill CookieValue column only).

  2. By using cookies (You will need to fill CookieName and CookieValue columns).

Important Note

You can update CookieName and CookieValue columns without restarting the bot by just simply saving the file while the bot is running.

  • CartWebhook (required) : The discord webhook channel where your cart webhook will be sent.

  • ErrorWebhook (required) : The discord webhook channel where the different errors will be sent such cart errors.

  • HideCheckout (optional) : Set this to true to prevent event name and event link from appearing in the checkout logs.

650B
ticketmaster.csv
Open

PreviousWetixNextSeetickets

Last updated