Seat Preevue developer docs
Seat Preevue shows a 360° view from a seat, on your booking pages, before your customers buy. These pages are for the developers who put it there: on a ticketing platform's pages, in your own site, or in an app.
Three ways to use it
| Mode | You add | You get | Start with |
|---|---|---|---|
| A. Core | One script tag, and a call from your own button | A full view in your page, styled by us, opened by your code | Quickstart: your own button |
| B. Hosted view | An <iframe> |
A view in a frame, with nothing to build | Quickstart: the hosted view |
| C. Headless | Calls from your server or app | Signed image URLs for your own viewer | Quickstart: headless |
If your venue sells through Spektrix, Tessitura TNEW, Criterion or a Viadukt site, there's a ready-made script for your platform: one tag, no code. See Ticketing platforms.
Already using an older Seat Preevue script (initSeatPreevue(…))? See Migrating: one URL change keeps your code working.
The hosts
| Host | What it serves |
|---|---|
https://assets.seatpreevue.com |
The SDK scripts (/sdk/v1/…), the hosted view (/embed/v1/) and the signed imagery (/v/…) |
https://connect.seatpreevue.com/v1 |
The API: sessions, seat resolution, events, and your keys and venues |
Both are needed in your Content Security Policy, if you have one.
Keys
Browsers use a publishable key (pk_live_…), safe in a page because it only works from the domains registered for it, or no key at all, when we register your domain. Servers use a secret key (sk_live_…), which must never reach a browser. See Keys and authentication.
What's here
- Quickstarts for each mode, and a guide for each ticketing platform.
- Content Security Policy and errors and messages.
- The API reference, generated from our API specification.
- The SDK changelog, with the Subresource Integrity hash of every file.