Postman Collection
Import the current Lottery Feed API contract into Postman with bearer auth, query examples, and sample request bodies.
Section
09 / 27
Live API examples
Jump from the docs to real public pages that use the same read models.
Endpoints
/postman-collection.jsonPostman v2.1 collection generated from OpenAPI.
Collection URL
The Postman collection is generated from the same OpenAPI contract as /openapi.json, so endpoint paths, parameters, and sample bodies stay aligned with the public API docs.
https://lotteryfeedapi.com/postman-collection.json
Import into Postman
Open Postman, choose Import, and paste the collection URL. The apiKey variable defaults to lf_test_demo_sandbox so latest-result and checker smoke tests run deterministically after import. Replace apiKey with an issued lf_live key only when you are ready to call production customer data. The collection also defines baseUrl and sandboxDrawDate so staging, production, and deterministic smoke tests can be switched without editing every request.
Collection URL: https://lotteryfeedapi.com/postman-collection.json baseUrl: https://api.lotteryfeedapi.com/v1 apiKey: lf_test_demo_sandbox sandboxDrawDate: 2026-06-21
Generated scope
The collection covers customer-facing /v1 read endpoints only. Each request description includes the required API key scope from OpenAPI, and query parameters keep the same descriptions as the public contract. Optional filters such as state, ball_count, game_code, and compact are included as disabled query presets, so the first run uses the broad documented endpoint and developers can enable filters deliberately. Private controls, collection diagnostics, source-probe payloads, and webhook signing secrets stay out of the public collection.
Cache and versioning
The route is cacheable for five minutes and should be refreshed after OpenAPI changes. Keep generated clients and tests pointed at /openapi.json when you need a formal schema; use Postman for fast manual integration checks.
Next: API changelog