TickerDocs
Tools

create_view

Creates a View: a saved screen that tells you when events enter it, by email or a destination, with an optional Digest.

When to use it

  • You want Ticker to keep a screen for you and tell you when events enter it, by email or in a Slack or Discord channel.
  • You want a Digest: the View's whole table sent at an hour you pick.
  • Try the predicate first with screen_events. To change a View that exists, use update_view.

Inputs

  • name (string, required): The View's name. Up to 120 characters.
  • predicate (object, default {}): The conditions, as a predicate, the same form screen_events takes. {} matches every event: pair it with max_firings_per_eval to cap what it sends.
  • enabled (boolean, default true): Set false to save the View paused.
  • channels (array of strings, required): Where Matches go: email sends them to your account's email address, and webhook sends them to the alert destinations attached to this View, such as a Slack or Discord channel. A View can carry both. One of email, webhook.
  • max_firings_per_eval (integer): The most events the View can match each time it runs, 25 when you leave it out. The events kept past the cap are not the largest moves, so narrow the predicate rather than rely on the cap. From 1 to 500.
  • apply_economic_floor (boolean): Leave out thin events, with few listings or a low median price. On when you leave it out. Set false to match every event.
  • delivery_target_id (uuid): An alert destination, from list_destinations, that gets each Match the instant it fires, besides email. Add destinations in the Ticker web app under Settings. Leave it out for email only.
  • notification_cadence (string): How often Matches may leave as email: immediate sends each one, hourly and daily gather them, and off records them with no email. A new View uses daily when you leave it out. Destinations ignore it: they get each Match the instant it fires. One of immediate, hourly, daily, off.
  • notification_mode (string): How email carries the Matches: instant sends one email per Match, batched holds them and sends them together in one email at the pace notification_cadence sets, and muted records them and sends no email. instant and muted override notification_cadence. A new View uses batched when you leave it out. Send batched: until 2026-11-30 Ticker also accepts digest, its old name, and saves it as batched; a response always says batched. One of instant, batched, muted, digest.
  • tags (array of strings): Labels that group and filter your Views in the app. They never change what the View matches or where it sends. Up to 5 items.
  • color (string): The accent color the app shows on the View. Cosmetic only. One of red, orange, amber, green, teal, blue, violet, pink.
  • digest (object): The View's Digest: its whole table sent at an hour you pick, each send an Issue with Movers, New and Gone against the previous Issue. Set enabled, hour (0 to 23, in your timezone), formats (the files the email links: csv, xlsx, pdf, md; the email always goes), destination_ids (destinations from list_destinations that also get each Issue), sections (which of movers, new and gone each Issue shows; the rest of the table always shows), extra_columns (absorption adds Absorbed 7d), table_columns (the Issue table's columns, in order, from list_screen_columns) and columns (whether the Digest page opens on the primary market's get-in or the secondary, resale, get-in). Leave it out and the Digest is off. A Digest is not notification_mode batched, which only groups Alert emails.
  • parking (string, default hide): Parking passes sold as their own event: hide (the default) leaves them out, only returns parking alone, include returns parking beside every other event. The View keeps this choice. One of hide, include, only.
  • listing_trigger (object): Instead of a predicate, tells you when a listing appears in one section of one event with at least min_quantity tickets at or under max_price, with or without fees as price_basis says. Listings with no price never match. One alert per listing, and again only at a lower price. Max and Ultra.

Examples

Email me each time an event in the next 30 days has its median price up 20% or more this week.

{
  "name": "Price up 20% this week, next 30 days",
  "predicate": {
    "all": [
      { "col": "ea.days_to_event", "op": "between", "val": [0, 30] },
      { "col": "ea.median_price_pct_7d", "op": ">=", "val": 20 },
      {
        "col": "ea.last_price_snapshot_date",
        "op": ">=",
        "val": { "days_ago": 1 }
      }
    ]
  },
  "channels": ["email"],
  "notification_mode": "instant"
}

Send me a Digest of every Zach Bryan show at 8 a.m. with a CSV and an Excel file, and no other emails.

{
  "name": "Zach Bryan shows",
  "predicate": {
    "all": [{ "col": "p.name", "op": "contains", "val": "Zach Bryan" }]
  },
  "channels": ["email"],
  "notification_mode": "muted",
  "digest": { "enabled": true, "hour": 8, "formats": ["csv", "xlsx"] }
}

Post New York events whose median price fell 15% or more this week to my Discord channel, at most 10 at a time.

{
  "name": "New York price drops",
  "predicate": {
    "all": [
      { "col": "v.city", "op": "=", "val": "New York" },
      { "col": "ea.median_price_pct_7d", "op": "<=", "val": -15 }
    ]
  },
  "channels": ["webhook"],
  "delivery_target_id": "9b3e2d1c-4a5f-4c8e-b7d6-1a2b3c4d5e6f",
  "max_firings_per_eval": 10
}

What comes back

  • The saved View: id, name, predicate, enabled, channels, notification_mode, notification_cadence and view_url. Pass id as view_id to the other View tools.
  • digest when you set one: the setting as saved, with live true when it is on and sending.
  • matches_note: a new View counts no Matches until it first runs. For the events that match now, run screen_events once with the same predicate.
  • An invalid predicate is refused with a message that names the problem, and nothing is saved.

Limits and quota

  • Changes something you own.
  • Reaches beyond Ticker: it can send alerts or read the web.
  • Each call spends one MCP request.
  • Views and stars is a limit on what you hold: past your plan's count the call is refused, names the plan that holds more, and saves nothing.
  • The Pro plan and above include Digests, and each plan sets how many can be on. A Digest past that count is refused with the plan that carries more, and the View is not saved.
  • A predicate that names a column your plan does not include is refused.
  • A destination that is not yours, or one that cannot take a Digest, is refused.

On this page