Skip to main content

Linking Methods

Open Accounts & Proxies → Account Manager and choose the method that fits your accounts:

MethodUse it for
Classic → Password loginLinking one account with its email and password.
Classic → Cookie ModeLinking one Ticketmaster account with a signed-in browser session.
Bulk → Paste / edit accountsPasting or typing up to 100 accounts into an editable table.
Bulk → Upload CSVImporting up to 100 account rows from a CSV file.
Bulk → CookiesImporting multiple Ticketmaster browser sessions from JSON.

The screenshots below come from Tikey's live interface. Any filled values are examples.


🧩 Classic Mode​

Classic mode allows you to add accounts one by one using a login form.

🔐 Single Mode Login​

Under Tickets Accounts, click Link Accounts → Ticketmaster. For Ticketmaster password login, prepare your Capsolver key and proxy group first.

  1. Select the region where you bought your tickets.
  2. Select a populated proxy group from Proxies Manager.
  3. Enter your account's email and password.
  4. Open Show OTP Method (optional) if you want to use an IMAP inbox or AYCD profile for verification codes. Otherwise, use None.
  5. Click Login and complete any requested verification.
Ticketmaster password login with region, proxy group, email, password, optional OTP methods, and Login.
The Ticketmaster form with OTP options expanded. Other providers show the fields needed for their login.

If password login is blocked, use Switch to Cookie Mode in the Ticketmaster login form to bring over a browser session.

Steps:​

  1. Install Cookie Editor from the Chrome Web Store.

  2. Visit the Ticketmaster login page in your browser and log in manually

  3. Open a Ticketmaster event page in the same region as the account you are linking, such as Ticketmaster US or Ticketmaster Netherlands.

  4. Open Cookie Editor on that event page. You can now export the full cookies JSON.

  5. In Tikey, choose the matching Region and proxy group, and enter the account's email and password. Click Switch to Cookie Mode.

  6. Paste the export into Paste full cookies JSON, then click Extract SOTC / SORTC / TMPT / id-token. Tikey fills the cookie fields automatically.

  7. Check the extracted values, then click Login.

Ticketmaster Cookie Mode showing the full JSON input, Extract button, and SOTC, SORTC, TMPT, and id-token fields filled with demo values.
Cookie Mode after extraction. The values shown here are examples; use the full export from your own signed-in browser session.

TMPT is needed for ticket transfers that use OTP. If Tikey shows TMPT missing, return to an event page for the selected region and export the cookies again.

📺 Need help? Watch this video (old video, you can now export the full JSON and paste it directly):
How to extract cookies and login to Tikey

⚠️ Make sure you're logged in completely before copying cookies.


📦 Bulk Mode​

Bulk Mode lets you paste accounts, upload a CSV, or import Ticketmaster cookies.


🧠 How it works​

  1. Click Bulk at the top right of the Account Manager.
  2. Select the provider tab, such as Ticketmaster or AXS.
  3. Click Bulk Login and choose Paste / edit accounts, Upload CSV, or Cookies.

✏️ Paste / edit accounts​

  1. Choose the Region and Saved proxy group for the accounts. For Ticketmaster, you can instead select Use an ISP proxy instead of a saved proxy group and enter the proxy.
  2. Paste one email:password pair per line, or copy the email and password columns from Excel or Google Sheets.
  3. Click Add to table and check the rows. You can edit cells or use + Add account to enter accounts manually.
  4. If several accounts share a password, select their rows, enter a Shared password, and click Apply password to … selected. Pasting only emails selects those rows automatically.
  5. Click Start bulk login.
Paste / edit accounts tab with a shared Ticketmaster region, example ISP proxy, shared password controls, and two demo account rows.
The region and connection apply to every row in this table. Passwords are masked, and you can review the accounts before starting.

📂 Upload CSV​

  1. Open the Upload CSV tab.
  2. Click Download Sample CSV for a starting template. Open Valid CSV Region codes to check the codes for your provider.
  3. Drop one CSV file into the upload area, or click Select a file.
  4. Click Start bulk login.
Upload CSV tab showing Download Sample CSV, Valid CSV Region codes, the file drop area, Import only, and Start bulk login.
Upload a CSV, or select Import only to save the account records without starting login.
Save accounts without logging in

For Paste / edit accounts and Upload CSV, check Import only — save accounts without logging in if you only want to store the account records. The submission button changes to Import accounts. This does not fetch tickets or verify the login.


📄 CSV Format Example​

Use the exact column names below. Each row needs an email, password, and region. Use the name of a proxy group that already exists in your Proxies Manager.

✅ Proxy Group Format:​

Region,Email,Password,Proxy Name
AXSUK,[email protected],ExamplePass123!,Demo proxies

✅ ISP Format (Ticketmaster only):​

Region,Email,Password,ISP
TMUS,[email protected],ExamplePass123!,proxy.example.com:8080:demo:password

You can include both connection columns in a CSV, but fill only one per row:

Region,Email,Password,Proxy Name,ISP
TMUS,[email protected],ExamplePass123!,Demo proxies,
TMUS,[email protected],ExamplePass123!,,proxy.example.com:8080:demo:password

ISP is only supported for Ticketmaster. Paste/edit and CSV import accept up to 100 accounts per submission.

Use the Cookies tab to add or update multiple Ticketmaster accounts from exported browser sessions.

Password and ISP are optional in the cookie JSON. You can add a password, a per-account isp proxy, or both. See the optional fields example below.

  1. Choose the Cookie region matching the exports. The form lists the required cookies for that region.
  2. For new accounts, choose a Proxy group or Use a shared ISP proxy. For existing accounts, Keep existing connection preserves their connection settings.
  3. Click Upload JSON, or paste the JSON into Or paste JSON. Use one email entry per account, with that account's full Cookie Editor export as its cookie array.
  4. Review the accounts ready count and any skipped entries, then click Import accounts.
  5. Open My Tickets → Refresh → Ticketmaster to fetch tickets and verify the imported sessions.
Bulk Cookies tab showing the cookie region, connection settings, JSON upload and paste options, and one demo account ready for import.
Bulk import expects an object with an email for each account, rather than the single cookie array used in Classic Cookie Mode.

For example, this shows the structure for two US accounts. Replace the demo arrays with each account's full export, keeping the cookie names, values, and domains:

{
{ "domain": ".auth.ticketmaster.com", "name": "SOTC", "value": "demo-sotc-1" },
{ "domain": ".auth.ticketmaster.com", "name": "SORTC", "value": "demo-sortc-1" }
],
{ "domain": ".auth.ticketmaster.com", "name": "SOTC", "value": "demo-sotc-2" },
{ "domain": ".auth.ticketmaster.com", "name": "SORTC", "value": "demo-sortc-2" }
]
}

Optional password and ISP​

You can optionally add a password, a per-account ISP proxy, or both to any account entry. To do this, use an object containing cookies instead of a plain cookie array:

{
"cookies": [
{ "domain": ".auth.ticketmaster.com", "name": "SOTC", "value": "demo-sotc" },
{ "domain": ".auth.ticketmaster.com", "name": "SORTC", "value": "demo-sortc" }
],
"password": "ExamplePass123!",
"isp": "proxy.example.com:8080:demo:password"
}
}
  • password is optional. Include it to save the account password. Omit it or leave it blank to keep an existing account's stored password.
  • isp is optional. Include it to use a proxy for this account instead of the connection selected in the form. Omit it to use the selected proxy group or shared ISP, or to keep an existing account's connection when neither is selected.

Use the account's full cookie export in cookies. You can remove either optional field from the example above. The form also shows this format under JSON format example (password optional) → Optional password / ISP.

Cookie import supports up to 10,000 accounts in a JSON file of up to 25 MB; it does not perform password login.


🌍 Region Codes​

Use the exact code in the CSV's Region column. The Valid CSV Region codes section in the upload form shows the codes for your selected provider.


🎟️ AXS Regions (interchangeable):​

  • AXSUK
  • AXSUS

For AXS, region is not strict — the same inventory is pulled regardless of region.


🏟️ Ticketmaster Regions:​

Region CodeLocation
TMNLNetherlands
TMDEGermany
TMATAustria
TMCHSwitzerland
TMDKDenmark
TMSESweden
TMBEBelgium
TMESSpain
TMUKUnited Kingdom
TMFRFrance
TMBAPBAP TMFR
TMCRFrance - Carrefour
TMLECLERCFrance - Leclerc
TMAUCHANFrance - Auchan
TMADIDASAdidas Arena
TMDEFENSEDéfense / Plénitude Arena
TMAEUnited Arab Emirates
TMUSUnited States
TMAUAustralia
TMNZNew Zealand
TMMXMexico
TMPLPoland
TMZASouth Africa
TMNONorway
TMCACanada
TMSGSingapore
TMPHPhilippines
TMCZCzech Republic
TM-AEGAEG

🎫 Eventim Group / Fnac:​

Region CodeLocation
EVTDEUGermany
EVTAUTAustria
EVTCHESwitzerland
EVTITAItaly
EVTFINFinland
EVTCOUKUnited Kingdom
FNACFnac Spectacles (France)

🎟️ Other bulk-login providers:​

Region CodeProvider
AccorAccor Arena
BlueMeoMEO Blueticket

🎫 SeeTickets / GigsAndTours:​

Region CodeDomain
SEETPTseetickets.com/pt
SEETESseetickets.com/es
SEETFRseetickets.com/fr
SEETBEseetickets.com/be
SEETCAseetickets.com/ca
SEETNLseetickets.com/nl
SEETCHseetickets.com/ch
SEETUKseetickets.com
SEETUSseetickets.us
GIGSNTgigsandtours.com

Backup domains (with -be) are also supported:

Region CodeDomain
SEETPTBACKseetickets.com/pt-be
SEETESBACKseetickets.com/es-be
SEETFRBACKseetickets.com/fr-be
SEETBEBACKseetickets.com/be-be
SEETCABACKseetickets.com/ca-be
SEETNLBACKseetickets.com/nl-be
SEETCHBACKseetickets.com/ch-be
SEETUKBACKseetickets.com/-be
SEETUSBACKseetickets.us-be
GIGSNTBACKgigsandtours.com-be

📌 Notes​

  • One region per row.
  • Start bulk login submits a login task; complete any requested verification before using the accounts.
  • Import only stores account records without logging in. Cookies imports browser sessions; refresh tickets afterward to verify them.
  • Fill only one connection field per CSV row: Proxy Name or ISP. ISP is for Ticketmaster only.
  • For a walkthrough from linking to fetching tickets, see How to Add Accounts.

Let us know if your region or domain isn’t listed!