Build powerful applications with LotterySpy through our developer API. Access approved historical lottery data and analytical resources, integrate LotterySpy research capabilities into your own applications, and create new digital experiences using the platform’s growing developer ecosystem.
Four simple steps to connect your application with the LotterySpy developer platform and start working with the resources available to you.
Register your developer account and confirm your email address to access the tools, documentation, and resources available to developers.
Create an API key from your developer dashboard and configure the access required for the LotterySpy resources your application will use.
Authenticate your application, send your first API request, and explore the response using the endpoint documentation and examples provided.
Handle responses and errors correctly, respect applicable usage limits, test your integration thoroughly, and prepare your application for production.
Authentication methods, API credentials, access scopes, and environments are provided according to the current developer service. Contact LotterySpy to confirm the live specification before integrating.
curl "https://www.lotteryspy.com/statistics/percentageApi" \
-H "Authorization: Bearer YOUR_API_KEY"
The current LotterySpy Percentage API is available through the live /statistics/percentageApi endpoint. Use the credentials issued for your developer account and never expose private API credentials in browser-side code.
The LotterySpy Percentage API exposes the same historical Percentage report used by the LotterySpy platform. Developers can request the report as structured JSON or retrieve the widget version for display in an external application.
https://www.lotteryspy.com/statistics/percentageApi
https://www.lotteryspy.com/statistics/percentageApi?format=widget
curl "https://www.lotteryspy.com/statistics/percentageApi" \\
-H "Authorization: Bearer YOUR_API_KEY"
curl "https://www.lotteryspy.com/statistics/percentageApi?format=widget" \\
-H "Authorization: Bearer YOUR_API_KEY"
| Parameter | Type | Description |
|---|---|---|
game_db | string | LotterySpy game database identifier. The current Percentage implementation defaults to gh_monday_special_nt when omitted. |
startEvent | integer | First historical event to include. The current implementation defaults to 1. |
EndEvent | integer | Last historical event to include. When omitted, the API uses the latest available event. |
format | string | Use widget to return the visual LotterySpy Percentage report instead of JSON. |
A successful JSON response includes the API version, selected game,
requested event range, current event, total draws, and the rendered
Percentage report in the widget field.
The widget endpoint returns a complete HTML document so the Percentage table can run in its own CSS and JavaScript environment. This is the recommended method when an integration needs the LotterySpy visual presentation rather than rebuilding the interface from JSON.
<script
src="https://www.lotteryspy.com/embed/percentage.js"
data-api="https://www.lotteryspy.com/statistics/percentageApi?format=widget"
data-game="gh_monday_special_nt">
</script>
For external websites, the embed script loads the LotterySpy report in an isolated iframe so the report can retain its own table styling, fonts, DataTables behaviour, and responsive layout.
Explore the platform capabilities developers may be able to integrate. Live endpoints, fields, authentication, and quotas are provided only when confirmed.
Build applications and research tools using LotterySpy historical draw-result data where API access is enabled for your account.
DocumentationIntegrate LotterySpy statistical and historical-analysis capabilities into applications, research projects, and data-driven experiences. The current live Percentage API is available through the Statistics API endpoint.
DocumentationExplore historical interval and timing analysis through developer integrations where Timing Key capabilities are supported.
DocumentationBring selected LotterySpy historical pattern-analysis capabilities into your own applications and research workflows where supported.
DocumentationConnect approved applications with publicly available LotterySpy Forecaster information where developer access is supported.
DocumentationIntegrate published LotterySpy prediction information into approved applications where the relevant developer capability is available.
DocumentationBuild applications and research tools using LotterySpy historical draw-result data where API access is enabled for your account.
DocumentationHistorical results form one of the core data foundations of the LotterySpy platform. Depending on your approved access, available resources may include draw results, game identifiers, dates, filtering, pagination, and related historical fields. The currently published Percentage API is available through LotterySpy's Statistics endpoint; additional historical-result endpoints should be confirmed against the live developer service before integration.
Confirm resource availability
Confirm authentication and access scope
Confirm endpoint and request parameters
Confirm response schema and usage limits
Test against the current developer environment
Integrate LotterySpy statistical and historical-analysis capabilities into applications, research projects, and data-driven experiences. The current live Percentage API is available through the Statistics API endpoint.
DocumentationLotterySpy statistical capabilities may include frequency, occurrence, intervals, positional analysis, comparative measures, and other historical research metrics. Calculation definitions, available fields, supported parameters, and response structures should be verified against the current API documentation before integration.
Confirm resource availability
Confirm authentication and access scope
Confirm endpoint and request parameters
Confirm response schema and usage limits
Test against the current developer environment
Explore historical interval and timing analysis through developer integrations where Timing Key capabilities are supported.
DocumentationTiming Keys are part of LotterySpy's historical-analysis framework and are designed to help researchers examine historical intervals, recurrence, and timing-related observations. Available endpoints, filters, response structures, and integration permissions depend on the live developer implementation.
Confirm resource availability
Confirm authentication and access scope
Confirm endpoint and request parameters
Confirm response schema and usage limits
Test against the current developer environment
Bring selected LotterySpy historical pattern-analysis capabilities into your own applications and research workflows where supported.
DocumentationLotterySpy pattern-analysis capabilities are intended for studying historical observations, relationships, repetitions, and analytical signals within available data. These outputs represent historical research information and should not be presented as guaranteed predictions of future lottery outcomes. Exact capabilities and response definitions should be confirmed through the current developer documentation.
Confirm resource availability
Confirm authentication and access scope
Confirm endpoint and request parameters
Confirm response schema and usage limits
Test against the current developer environment
Connect approved applications with publicly available LotterySpy Forecaster information where developer access is supported.
DocumentationForecaster resources may provide access to publicly presented information such as forecaster profiles, published information, and performance-related data where those resources are made available through the developer platform. The specific fields and permissions available to each integration depend on the approved API access.
Confirm resource availability
Confirm authentication and access scope
Confirm endpoint and request parameters
Confirm response schema and usage limits
Test against the current developer environment
Integrate published LotterySpy prediction information into approved applications where the relevant developer capability is available.
DocumentationPublished predictions are presented as part of LotterySpy's broader research and forecasting ecosystem. They must not be represented as guaranteed lottery outcomes. Developers integrating this information are expected to preserve LotterySpy's standards of transparency, responsible presentation, and clear distinction between historical analysis, forecasts, and future uncertainty.
Confirm resource availability
Confirm authentication and access scope
Confirm endpoint and request parameters
Confirm response schema and usage limits
Test against the current developer environment
LotterySpy Developer access is designed to support different stages of integration, from evaluation and development to production deployments and strategic partnerships. Availability, request limits, quotas, commercial terms, and additional access requirements may vary by integration and are confirmed as part of the developer access process.
Common HTTP status codes that an integration may encounter. The exact response body should be confirmed against the current API specification.
| Status | Meaning | Description |
|---|---|---|
| 200 | OK | The request was successfully received and processed. |
| 400 | Bad Request | The request could not be processed because one or more submitted parameters are invalid, missing, or incorrectly formatted. |
| 401 | Unauthorized | Authentication is required, or the credentials provided with the request are missing, invalid, or no longer valid. |
| 403 | Forbidden | The request was understood, but the authenticated application or account does not have permission to access the requested resource. |
| 404 | Not Found | The requested endpoint, resource, or record could not be found. |
| 429 | Too Many Requests | The client has exceeded an applicable request or usage limit. Reduce the request rate and try again according to the applicable access policy. |
| 500 | Internal Server Error | An unexpected error occurred while processing the request. If the problem persists, contact LotterySpy developer support with the relevant request details. |
Use the language and HTTP tooling that fits your application. Official SDK availability should be confirmed with LotterySpy before being described as supported.
curl "https://www.lotteryspy.com/statistics/percentageApi" \
-H "Authorization: Bearer YOUR_API_KEY"const res = await fetch(
"https://www.lotteryspy.com/statistics/percentageApi",
{
headers: {
Authorization: "Bearer YOUR_API_KEY"
}
}
);
const data = await res.json();import requests
res = requests.get(
"https://www.lotteryspy.com/statistics/percentageApi",
headers={"Authorization": "Bearer YOUR_API_KEY"},
)
data = res.json()$ch = curl_init(
"https://www.lotteryspy.com/statistics/percentageApi"
);
curl_setopt($ch, CURLOPT_HTTPHEADER, [
"Authorization: Bearer YOUR_API_KEY"
]);
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
$data = json_decode(curl_exec($ch), true);
curl_close($ch);Have an idea for an integration, need access to the LotterySpy Developer Platform, or interested in building a strategic partnership? We're here to help you understand the platform, explore available capabilities, clarify technical requirements, and identify the right path for your project. Contact our team before you begin development so we can confirm current API availability, supported resources, access requirements, and integration guidelines.
Need developer access or questions about authentication, integrations, available resources, or technical requirements? Our Developer Support team is here to help you get started, understand the platform, and guide you through the integration process from initial access to implementation.
developers@lotteryspy.comDeveloper integrations must comply with LotterySpy applicable terms, privacy and data-protection requirements. Developers are expected to use our platform resources responsibly and uphold LotterySpy's standards of integrity, transparency, and security.
Review Developer Terms →The LotterySpy Developer Platform will continue to evolve. API capabilities, documentation, access requirements, usage limits, and supported resources may change as the platform grows. Contact us for current information about developer availability and integration updates.
Contact Developer Support →