get_event_demand_chart

Reads only.

Use this for one event's daily demand series, interest and sales levels. Use get_event_price_chart instead for its daily prices and inventory, and get_event_analytics_history for its signal columns over time. Daily demand time series for one event (event_demand_daily), ordered snapshot_date ASC. Two signals: interest = people currently browsing/watching the event's listings (attention), sales = recent ticket sales. Both are marketplace rolling-window LEVELS, not daily flows: a value is 'the level of the window as of that day', so read the day-over-day DELTA as momentum and NEVER report a value as a count of tickets bought today. Columns per row: first/last/min/max_urgency_lt and first/last_velocity_lt capture the long-window level's path within the day (first vs last = intraday drift); max_urgency_st / max_velocity_st are the day's short-window peaks (spikes); snapshot_count = intraday samples behind the rollup; last_snapshot_time = when the day's final sample landed. Signal values are nullable ints (null = not observed that day). History starts 2026-07-17, so history is shallow initially. Use after screen_events / get_event_analytics to see whether demand is building or fading into the event. Answers {event_id, event_name, local_date, venue_name, sub_category_id, range, rows}: rows is the series and the identity fields are what it is OF, so a chart legend reads a name and never an id. rows:[] when no rows. A rendered chart image of the series is included by default; pass render:false for data only.

Parameters