> ## Documentation Index
> Fetch the complete documentation index at: https://docs.eventory.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Watchlist platforms

> The platform keys the watchlist validates, the retired aliases it still accepts, and the discovery monitors that watch an artist or venue instead of an event.

The `website` field on a watchlist item names the platform to monitor. These keys are
**separate from the Live Availability platform keys** on
[Supported platforms](/guides/platforms) — the watchlist covers a much wider set, and
the two vocabularies do not overlap in spelling (`ticketmaster` here, `tm` there).

## `website` is not an allowlist

Any string is accepted. For the platforms listed below, `event` is validated against
that platform's — and often that region's — id format, and a mismatch is rejected with
`400`. For **anything else, validation is skipped** and the item is stored exactly as
sent.

<Warning>
  A typo in `website` does not return an error. It creates a watchlist item that nothing
  will ever monitor, and it will sit in your watchlist looking healthy. Check the value
  against this page before you create items programmatically.
</Warning>

## Platforms with a validated `event` format

Current as of 17 September 2026.

<Columns cols={3}>
  <div>
    * `allaccess`
    * `artist_new_events`
    * `atleticomadrid`
    * `axs`
    * `banquetrecords`
    * `billetterie.accorarena`
    * `billetterie.adidasarena`
    * `billetterie.aegpresents`
    * `billetterie.bouffesdunord`
    * `billetterie.fff`
    * `billetterie.ffr`
    * `billetterie.parisladefense`
    * `blueticket`
    * `bo26.myticket.de`
    * `dice`
    * `eticketing`
    * `eticketing-uk`
    * `etihadarena`
    * `etix`
    * `eventim`
    * `eventim_artist_new_events`
    * `eventim_venue_new_events`
    * `evenue.net`
    * `f1.abudhabi`
  </div>

  <div>
    * `f1.tickets`
    * `fanki`
    * `fansale`
    * `feverup`
    * `fifa`
    * `funcode`
    * `gpcanada`
    * `gpmonaco`
    * `gpmonza`
    * `gpsingapore`
    * `jazzopen-stuttgart`
    * `laoreja`
    * `meo-blueticket`
    * `milano-cortina`
    * `mlb.tickets`
    * `moviestararena`
    * `nfl-tmtickets`
    * `nhmpe.seetickets`
    * `onkelz.myticket.de`
    * `paylogic`
    * `platinumlist`
    * `psg`
    * `royalhall`
    * `seatgeek`
  </div>

  <div>
    * `seatpick`
    * `seetickets`
    * `sport.ticketone`
    * `stubhub`
    * `ticketek`
    * `ticketera`
    * `ticketmaster`
    * `ticketpoint`
    * `ticketportal`
    * `tickets.oneboxtds`
    * `tickets.uefa`
    * `ticketswap`
    * `ticketweb`
    * `tickpick`
    * `twickets`
    * `venue_new_events`
    * `viagogo`
    * `vivatickets`
    * `wiederverkaufsplattform`
    * `wienticket`
    * `ztwen-jussyun`
  </div>
</Columns>

If you get the format wrong, the `400` tells you what was expected:

```json theme={null}
{ "error": "One or more IDs are invalid for ticketmaster. Example: 0200642CF18CAA24" }
```

The `Example` is a real, valid id or URL for that platform — copy its shape.

## Discovery monitors

Four keys do not watch a single event. They watch an artist or venue page and fire when
**new events are announced** there, which is how you catch an on-sale before you know
the event id.

| `website`                   | Watches                    | What to put in `event` |
| --------------------------- | -------------------------- | ---------------------- |
| `artist_new_events`         | A Ticketmaster artist page | The artist URL         |
| `venue_new_events`          | A Ticketmaster venue page  | The venue URL          |
| `eventim_artist_new_events` | An Eventim artist page     | The artist URL         |
| `eventim_venue_new_events`  | An Eventim venue page      | The venue URL          |

Everything else about the item works normally — the filters, `task_active`, and the
notifications the Notifications API delivers.

## Retired aliases

"Ticketmaster Early" was merged into Ticketmaster on 8 September 2026. The old keys are
still accepted on create and silently stored as `ticketmaster`:

`ticketmaster_preload` · `ticketmaster_early` · `ticketmaster early` · `tm_preload` · `tm`

Existing integrations keep working unchanged. New ones should send `ticketmaster`.

<Note>
  Because the alias is rewritten on the way in, an item created with `tm` comes back from
  `GET /watchlist` with `website: "ticketmaster"`. That is not a bug — do not treat it as
  a failed write.
</Note>

## Filters are not supported everywhere

A filter that the target `website` and `region` combination does not support is
**dropped rather than rejected**: the create or update succeeds, the stored item simply
has that filter unset, and the response lists what was dropped in `ignored_fields`.

```json theme={null}
{
  "item": { "id": 123, "website": "stubhub", "platinum_tickets": null },
  "items": [ { "id": 123 } ],
  "createdIds": [123],
  "ignored_fields": ["platinum_tickets", "no_presale"]
}
```

If a filter you set appears to have disappeared, check `ignored_fields` on the response
that created or updated the item.