API documentation
OpenAPI Specification
Machine-readable API contract for SDK generation, integration tests, and customer onboarding.
Section
08 / 27
01Introduction02Quickstart03Polling and integration04Sandbox fixtures05SDK starter06Embeddable widgets07API playground08OpenAPI spec09Postman collection10API changelog11Authentication12API key scopes13Freshness levels14Source confidence15Status monitoring16Rate limiting17Get countries18Get states19Get lotteries20Get lottery21Get schedules22Draw years23Lottery results24History export25Number frequency26Result checker27Error handling
Live API examples
Jump from the docs to real public pages that use the same read models.
Latest results browserSee the compact public result model with filters and draw dates.
Lottery catalogFind game names, states, ball counts, latest numbers, and API guides.
Maryland Pick 3 API guideOpen a concrete endpoint example using the same game shown in snippets.
Pricing and limitsCompare freshness targets, request limits, and integration features.
Customer integration centerSign in to check API keys, usage, webhook delivery, plan limits, and the next recommended action.
OpenAPI contractUse the machine-readable contract for code generation and integration tests.
Endpoints
GET
/openapi.jsonOpenAPI 3.1 JSON contract.
Specification URL
The public spec is available without requiring customer credentials so developers can inspect the contract before requesting API access.
GET /openapi.json
Versioned alias
The same contract is also available under the versioned API namespace. If API auth is enabled for /v1, use the public /openapi.json URL for unauthenticated schema discovery.
GET /v1/openapi.json
Contract scope
The specification covers the compact public /v1 contract, including documented authentication, filters, responses, and errors.
Next: Postman collection