Plan delivery levels
How result freshness targets are classified for standard, premium, and enterprise subscriptions.
Section
13 / 27
Live API examples
Jump from the docs to real public pages that use the same read models.
Standard subscription target
Lottery Feed API uses F1 to F7 delivery levels so pricing, account screens, API docs, and support copy describe plan delivery delays consistently. The current standard subscription uses F3 2h access, applying a 2-hour plan delivery delay after the feed first stores or observes a result.
Latency levels
F1 Daily: after a 24-hour plan delivery delay F2 4h: after a 4-hour plan delivery delay F3 2h: after a 2-hour plan delivery delay F4 1h: after a 1-hour plan delivery delay F5 30m: after a 30-minute plan delivery delay (premium) F6 15m: after a 15-minute plan delivery delay (enterprise/custom) F7 5m: after a 5-minute plan delivery delay (enterprise/custom)
Publication basis
F1-F7 measure plan delivery delay after the feed first stores or observes a result. Collection lag from official publication is measured separately. If an official lottery source delays publication, including during major jackpot events or additional validation processes, the feed can only publish after the official result becomes available. F1-F7 are plan delivery-delay targets, not guarantees of ingestion speed or uptime. The delay clock starts after the feed first stores or observes a result; upstream publication and ingestion can add time before that point.
Commercial expectation
Public, pricing, and customer subscription copy must describe F1-F7 as plan delivery delays, not as ingestion SLAs or fixed draw-to-delivery promises.
Ongoing improvements
Recent platform work corrected draw schedules across lotteries, including intraday and day-specific timings, increased polling frequency, and improved result detection and processing. Update times are already improving and should continue improving gradually where source access permits. - Corrected draw schedules across lotteries, including intraday draws and day-specific timings. - Increased polling frequency around expected publication windows instead of relying only on broad batch checks. - Improved result detection and processing so newly published draws are recognized and written sooner.
Near real-time delivery
F6 and F7 reduce the plan delivery delay after feed storage. They do not create an ingestion SLA; any source-specific ingestion commitment requires separate review. Treat F6-F7 as reviewed access levels. Any additional ingestion, redundancy, or source-coverage commitment must be scoped separately. F7 applies a 5-minute plan delivery delay and is not included in standard subscriptions. It does not guarantee five-minute ingestion from draw time or official publication. If low end-to-end latency is required, capture the exact game list, official-publication evidence, ingestion expectations, jurisdictions, and redundancy needs separately from the F-level plan delay.
Next: Source confidence