Viagogo is a global secondary-market ticket exchange. We build the seller-side automation around it — listings, pricing, and fulfilment — and we host and monitor what we build.
Viagogo, part of the StubHub group, is one of the largest resale marketplaces for event, sport, and entertainment tickets. For anyone selling at volume, the manual workflow does not scale: hundreds of listings across hundreds of events, each needing its price kept competitive as the event approaches.
Integration is about removing that manual work safely. Create and update listings programmatically, respond to sales, and keep pricing current — with guard rails, because an automated pricing mistake on a live marketplace is expensive and fast.
Reading the documentation is the easy half. These are the areas that decide whether an integration takes weeks or months — and the ones we scope carefully before quoting.
Sellers at volume rarely live on one marketplace. The same inventory is often listed in several places, which brings back the oldest problem in distribution: never sell the same item twice, and withdraw it everywhere the moment it goes.
That is the same inventory-synchronisation discipline as a travel channel manager, applied to ticketing. It is work we do, and the non-negotiable part is that it fails safe — a broken feed must stop and alert, not keep trading on stale data.
Marketplace API access for sellers is account- and agreement-dependent rather than something anyone can simply switch on. The first thing we do on any engagement is establish what access you actually have, because it determines what can responsibly be built.
Yes, with guard rails that are not negotiable: a price floor, a sanity check on the inputs, and a circuit breaker that stops the run rather than acting on bad data. An automation that drops prices because a data source was briefly unavailable can do a lot of damage very quickly.
Not if it is built to the interfaces the platform supports. We do not build tooling that drives a seller portal in ways the platform does not sanction, because the consequences land on your account and we would rather protect it. If what you have in mind would need that, we will say so early.
Yes, and that is where most of the value is. It also makes a single source of truth essential, along with fast withdrawal everywhere once something sells.
Yes. Reviewing and hardening an existing automation — usually adding the fail-safes and the monitoring it never had — is a common engagement, and cheaper than a rebuild.
We are usually working in several of these at once, which is how we know where each one bites. See all integrations for the full list.