Plans for API integrations and personal analytics.
Free Beta registration is available without a card. Paid plan prices are shown in EUR, USD, and GBP for planning, but paid activation is not available through the website.
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. F6-F7 delivery is handled as enterprise work.
F3 2h is the current standard plan delivery delay. Upstream publication and feed ingestion happen before that delay clock starts.
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.
Personal analytics windows expand from 7 days on Free to 1 year on Pro. Faster result delivery follows the selected plan's documented target and may also be enabled as a reviewed account add-on; it is not a delivery guarantee.
Access model
Selected currency
USD
Free Beta registration
Open
Paid plans
3 planning options
Paid activation
Not currently available
Free
USD 0.00 / month
Explore the API contract with the F1 Daily plan delivery delay and no billing commitment.
Daily limit
4
Monthly limit
100
Update level
F1 Daily
Webhooks
Contact us
Support
Docs only
F1 Daily makes results available after a 24-hour plan delivery delay. 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.
Webhook delivery is disabled by default. Contact us for a scope, data-rights, and reliability review before activation.
Request webhook accessUsage limits without surprises.
Free Beta daily and calendar-month limits are enforced per workspace, so additional API keys do not multiply them. The daily window resets at 00:00 UTC; the monthly window resets on the first day of each month at 00:00 UTC.
Daily hard limit
Free Beta requests share one workspace limit that resets at 00:00 UTC. Limited requests return HTTP 429 with Retry-After and X-RateLimit-Reset so clients can pause cleanly.
Monthly hard limit
The Free Beta calendar-month limit is enforced for the whole workspace and resets on the first day of each month at 00:00 UTC.
No silent overage
The API returns HTTP 429 when the workspace reaches either hard limit. Additional keys cannot multiply Free Beta capacity; higher-volume access requires review before extra traffic is approved.
Access lifecycle
Review the API contract now. Create and verify your account when registration is open; API key issuance is activated separately when available.
01
Create account
Every self-service workspace starts on Free and owns its API keys, usage evidence, and support context.
02
Choose an access path
Join the Free Beta when registration is open. Paid plans remain future planning options and cannot be activated on this site.
03
Use the API
Verified Free Beta workspaces share one daily request limit across every active API key and can review usage in the account area.
API keys
Verified accounts are prepared for scoped API keys, one-time secret display, rotation, and immediate revocation when API access is activated.
Source confidence
Customer-safe confidence labels distinguish confirmed official evidence from reviewed, cross-checked, fallback, and operator-reviewed sources. Rows without sufficient public evidence are not promoted as trusted examples.
Planning currencies
Published plan estimates are available in EUR, USD, and GBP. Paid activation is not currently available through the website.
Plan delivery delay
The current standard subscription uses F3 2h access, applying a 2-hour plan delivery delay after the feed first stores or observes a result.
Delivery levels
F1-F7 measure plan delivery delay after the feed first stores or observes a result. Collection lag from official publication is measured separately. 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.
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. 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.
01
Corrected draw schedules across lotteries, including intraday draws and day-specific timings.
02
Increased polling frequency around expected publication windows instead of relying only on broad batch checks.
03
Improved result detection and processing so newly published draws are recognized and written sooner.
F1
after a 24-hour plan delivery delay
Plan access starts 24 hours after the feed first stores or observes a result.
F2
after a 4-hour plan delivery delay
Plan access starts 4 hours after the feed first stores or observes a result.
Choose the next step for your integration.
Review the API contract, create a free workspace, or discuss custom ingestion and delivery requirements before production traffic.
Read the API contract
Start with the public API docs, OpenAPI contract, sandbox fixtures, and compact result examples before choosing an access plan.
Open API docsCreate a workspace
Create an account when you are ready to issue keys, test usage limits, request reviewed webhook access, and track request evidence.
Create accountPlan a production rollout
Contact us when you need custom freshness, higher limits, source-confidence review, or enterprise webhook delivery requirements.
Contact usPlan details
The public page explains access limits and plan delivery delays. API key records and request evidence remain private to the customer account.
What counts as one API call?
Every authenticated request to a /v1 endpoint counts as one call. Public docs and public website pages are not metered.
Which planning currencies are shown?
Public plan estimates are available in EUR, USD, and GBP. Paid activation is not currently available through the website.
Is scraper/source data included?
Customer API responses use compact result read models. Raw source probes, request logs, and correction tools stay inside the protected feed operator admin.
Can official sources delay results?
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.
Why is near real-time custom?
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. Availability depends on the requested games, jurisdictions, and reviewed delivery requirements.