TickerDocs
Tools

research_event

Reads the event's research brief, as its page shows it: recent dated coverage of the event and its performers, with sources.

When to use it

Inputs

  • event_id (string, required): The event, by its Ticker id (ev plus ten characters), as search_events and the other tools return it.
  • force (boolean): Gather a fresh brief even when one from the last 24 hours is saved. Set it only when the saved brief is too old for you.

Examples

Why did prices for this show jump this week?

{ "event_id": "ev3rp4z4zhq1" }

Research this game again. I want the latest coverage, not the saved brief.

{ "event_id": "ev5t9h2w7k3c", "force": true }

What comes back

  • research: the brief, or null when the event has none saved and none could be gathered.
  • status ok carries summary and payload.items: one item per fact, with its date, the fact and, when there is one, the url it came from. approx true marks a date the source gave only roughly.
  • status empty means nothing recent turned up, and error means the brief could not be gathered this time. Neither is saved, so a later call looks again.
  • fetched_at says when the brief was gathered, and cached true means it is the saved brief rather than a fresh one. When a fresh brief cannot be gathered, the saved one is served whatever its age.

Limits and quota

  • Changes something you own.
  • Reaches beyond Ticker: it can send alerts or read the web.
  • A fresh result spends one Event research; a cached result and an empty one spend nothing.
  • Covers news and posts from the last 28 days. Ticket listing pages are left out, so results are coverage, not listings.
  • Live numbers, like availability or odds, come from the market tools.
  • The Max plan and above include events that have already taken place.

On this page