TIXMAFIA

No marketplace publishes other people's sales — the official API returns only your own. Every tracker on the market, including the ones you pay for, infers sales by polling the public board and diffing it. That is exactly why two of them show identical sales at identical prices: same public data, same inference.

The precision is in the classification, so this splits what others merge:
Reported — read from an actual sales record, not a board that changed. A seller account with invoice-level access sees real transactions, and nothing inferred outranks them. Capture an invoice page with the companion and tell it whether the rows are your own sales or the whole event's.
Confirmed — the listing is still up with fewer tickets. Sellers almost never hand-edit a quantity downward, so this is as close to a receipt as the public board gets.
Likely — the whole listing is gone. Sold out, pulled or expired look identical from outside, so it is counted separately rather than folded into one flattering total.
A seat that reappears at another price is a reprice and is dropped entirely. Matching on section + row + price — or the marketplace's listing id when the page exposes one — is what keeps two same-priced listings in one section from being confused.

Set IMAP_HOST, IMAP_USER and IMAP_PASS in the environment, using a dedicated app password you can revoke on its own. The mailbox is opened read-only, only recent messages from expected sender domains are scanned, and a number counts as a code only when a word like "code" or "OTP" sits next to it — an order reference is never mistaken for an OTP. Nothing is deleted, moved or marked as read.

Access is granted per partner, not self-serve. Email api.support@stubhub.com (or affiliates@viagogo.com) describing the tool and your rough volume; they issue a client id, a client secret and the token URL.

Then set these in the environment and restart: STUBHUB_CLIENT_ID, STUBHUB_CLIENT_SECRET, STUBHUB_TOKEN_URL — and the VIAGOGO_ equivalents. MARKETPLACE_SANDBOX=0 switches to production; MARKETPLACE_WRITES=1 allows pushing changes.

Both default to the safe side. The client starts in sandbox and read-only, because a wrong write against a live seller account cannot be undone. Watch a few pulls land correctly before you let it write.

Their API lets a listing carry our identifier. Every listing pushed from here carries its position id, which turns reconciliation from guessing by event name into an exact join — and makes a repeated create idempotent instead of a duplicate. A full pull is treated as complete; an incremental one never is, because a delta shows only what changed and treating it as the whole picture would deactivate everything else.

Strip anything personal first — buyer names, addresses, payment details. Nothing here needs them, and what does not get pasted cannot leak.

Rows imported this way land as reported sales, the same tier as invoice data, because they come from a record rather than from a board that changed. If the analysis says listings rather than sales, that is the tell: an offer has a price but no date, a trade has both.

Marking a reduction done applies it to the listing here as well, so the books match what you just did on the marketplace. It does not reach out and change anything by itself.

Open each ticket in the provider's own app and confirm the barcode actually renders, then mark it here. An app that refuses to show a code is a box-office visit when you find it a week early, and a lost sale when you find it at the gate.

Tickets marked dynamic cannot be put in a delivery link, and that is not a limitation worth working around: a rotating code regenerates every few seconds, so a captured frame is already dead by the time a buyer reaches the gate. Those go through the transfer queue, early enough that a broken app is still fixable.

Captures arrive as drafts, never straight into the books. Cost is left at zero — a page listing your seats does not know what you paid for them, so fill it in on the position rather than letting a guess become a P&L number.

1. Open chrome://extensions and turn on Developer mode.
2. Click Load unpacked and pick the companion folder inside this project.
3. Open the extension, expand Connection settings, paste the token above and the dashboard URL, then Save.
4. Go to a "my tickets" page on Ticketmaster, AXS, the Eventim chain, TicketOne, Vivaticket or See Tickets — or a marketplace event page on Viagogo, StubHub, Ticombo or Gigsberg — and hit Capture.

Retailer pages become inventory drafts; marketplace pages become Sales Tracker snapshots. On a marketplace, tell the extension whether the prices shown are gross or seller payout — comparing one against the other is how a tracker ends up lying to you.

CSV works today: export from the marketplace, import on the Inventory page, export back when you need to push changes.

Browser session is the next step — you sign in yourself and the tool works inside that session. There is no automated mass login with proxy rotation and CAPTCHA solving here: that stack breaks every time a platform updates its bot detection, and a repricer that dies quietly on a match day is worse than none.

Official API is the best case where a partner programme exists and you are accepted into it.