LEAP Implementation GuidanceMultiple API Guidance - Interactive WalkthroughInteractiveWalkthrough - v1.0
One live event, two APIs: from Forecast to live Concurrent Streams
Follow a single championship broadcast from 30 days out to the moment its stream closes. Before the stream opens, the Forecast API is the plan. Once the stream opens, the Concurrent Streams API is the authoritative signal. This example carries both a common content.id and a source-qualified Extended Content ID (content.data[].cids), either of which can correlate the forecast, live stream measurements, and OpenRTB bid requests when consistently preserved. Each call has three views: when it is made, what comes back, and what changed since the previous call. All values are made-up examples.
Before the event
Forecast API
Streams range and ad inventory per event. Polled daily, then hourly as the event nears.
stream openshandoff
While the stream is open
Concurrent Streams API
stream closescompare
After the event
Post-event review
saved snapshots from both APIs
Actual peak against the forecast range, pods against plan, request volume against streams.
Shared Key — Cross-API Identity Correlation
One event — shared identity via Content ID OR source-qualified Extended Content ID
Forecast APIBefore the event
JOIN KEY — OPTION 1 Content ID
events[].content.id
event-content-12345
OR
JOIN KEY — OPTION 2 Extended Content ID
events[].content.data[].cids[]
shared-content-id-12345
Source: id-provider.example
events[].content.data[].name
id-provider.example
Source identifying the Extended Content ID
events[].id
event-content-12345
Forecast event record ID; not necessarily equal to content.id
Same external-ID source as the Forecast API example
streamsdata[].mediastreams[].eventstart
1794099600000
Timing helps validate a match but is not a unique key
OpenRTBBidstream
JOIN KEY — OPTION 1 Content ID
app.content.id
event-content-12345
OR
JOIN KEY — OPTION 2 Extended Content ID
app.content.data[].cids[]
shared-content-id-12345
Source: id-provider.example
app.content.data[].name
id-provider.example
Source-qualified Extended Content ID
site.content.id / site.content.data[].cids[]
Same example values when passed
Alternative field paths for site inventory
BidRequest.id
bid-request-98765
Auction ID; not a content identifier
Arrow keys move between calls
What it means
Streams against forecast live total = sstreams + cstreams, both regions
Forecast API snapshots 0 calls
first valuechanged since the previous callKeep every snapshot. The post-event review compares them with what actually happened.
Concurrent Streams snapshots 0 calls
Based on the LEAP Forecast API and Concurrent Streams API draft specifications and the implementation guidance prepared for public comment (Oct. 2026). All events, stream counts, region mappings, break times, and bid-request volumes are illustrative. QPS and pacing calculations are worked examples based on stated assumptions, not prescribed implementation defaults. This walkthrough illustrates API 1.0 behavior only.
