# Texas Lottery Winning Stores: Prize Claims by Retailer (`jackpotledger/texas-lottery-prize-claims-by-retailer`) Actor

Rank Texas Lottery retailers by prizes claimed from tickets they sold: number of claims, total and largest prize, by game, for any date range. Filter by city, county, game and minimum prize. No player names. Export to JSON, CSV or Excel.

- **URL**: https://apify.com/jackpotledger/texas-lottery-prize-claims-by-retailer.md
- **Developed by:** [JackpotLedger](https://apify.com/jackpotledger) (community)
- **Categories:** Business, Automation, Other
- **Features:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $15.00 / 1,000 results

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

[![Texas Lottery Winning Stores: Prize Claims by Retailer](https://scrapers.lat/banners/texas-lottery-prize-claims-by-retailer.png)](https://console.apify.com/actors/tveRQtTj38yFOvIDk/input)

## Texas Lottery Winning Stores: Prize Claims by Retailer

Find the Texas stores that sold the most winning lottery tickets. Prize claims are added up per selling retailer, and per game if you want, for any date range. Player names are never included.

Here is one real record from this actor.

```json
{
  "state": "TX",
  "rank": 1,
  "retailer_id": "1435398",
  "retailer_name": "SUPER K",
  "address": "5860 SAN FELIPE ST",
  "city": "Houston",
  "zip": "77057",
  "county": "Harris",
  "game_category": "All games",
  "claims": 1,
  "prize_total_usd": 5000000,
  "largest_prize_usd": 5000000,
  "first_claim_date": "2026-10-26",
  "last_claim_date": "2026-10-26",
  "period_from": "2026-09-30",
  "period_to": "2026-10-30",
  "source": "Texas Lottery Commission",
  "source_url": "https://www.texaslottery.com/",
  "observed_at": "2026-10-30T22:37:39.845Z"
}
```

**[Input](https://apify.com/jackpotledger/texas-lottery-prize-claims-by-retailer/input-schema) | [Output](https://apify.com/jackpotledger/texas-lottery-prize-claims-by-retailer/output-schema) | [Pricing](https://apify.com/jackpotledger/texas-lottery-prize-claims-by-retailer/pricing)**

![Coverage](https://img.shields.io/badge/Coverage-Texas-blue)
![Output](https://img.shields.io/badge/Output-JSON%20%7C%20CSV%20%7C%20Excel-orange)
![Billing](https://img.shields.io/badge/Billing-Pay%20per%20result-brightgreen)

### Table of contents

- [What you get](#what-you-get)
- [Input and filters](#input-and-filters)
- [Use cases](#use-cases)
- [Coverage and freshness](#coverage-and-freshness)
- [Pricing](#pricing)
- [Comparison with other Apify actors](#comparison-with-other-apify-actors)
- [Related JackpotLedger actors](#related-jackpotledger-actors)
- [FAQ](#faq)
- [Run it through the Apify API](#run-it-through-the-apify-api)

### What you get

One record per store (and game) with the number of claims, total prizes, the largest single prize and the first and last claim dates in the period, ranked by total prizes.

Each record can carry these 20 fields. A field the source does not publish for a record comes back as `null`.

| Field | Type | Description |
|---|---|---|
| `state` | string | US state (TX) |
| `rank` | integer | Rank by total prizes in this run |
| `retailer_id` | string | Texas Lottery retailer number |
| `retailer_name` | string | Store name |
| `address` | string | Street address |
| `city` | string | City |
| `zip` | string | ZIP code |
| `county` | string | County |
| `game_category` | string | Game, or All games when not split |
| `claims` | integer | Number of prize claims |
| `prize_total_usd` | integer | Sum of prizes claimed |
| `largest_prize_usd` | integer | Largest single prize claimed |
| `first_claim_date` | string | First claim date in the period |
| `last_claim_date` | string | Last claim date in the period |
| `period_from` | string | Period from |
| `period_to` | string | Period to |
| `source` | string | Publisher of the official data |
| `source_url` | string | Public page where the publisher shows this data |
| `observed_at` | string | Time this record was collected (ISO 8601, UTC) |
| `error` | string | Only present on the single no-data or failure record. That record is never charged. |

### Input and filters

All inputs are optional.

| Field | Type | Required | Default | Description |
|---|---|---|---|---|
| `dateFrom` | string | no | (none) | First date to include, as YYYY-MM-DD. Leave empty for the last 30 days. |
| `dateTo` | string | no | (none) | Last date to include, as YYYY-MM-DD. Leave empty for today. |
| `retailerNames` | array | no | (none) | Optional partial-match filters on the store name, for example 7-ELEVEN. |
| `retailerIds` | array | no | (none) | Optional official retailer numbers. |
| `cities` | array | no | (none) | Optional city filters. |
| `zipCodes` | array | no | (none) | Optional 5-digit ZIP codes. |
| `counties` | array | no | (none) | Optional county filters. |
| `gameCategories` | array | no | (none) | Optional game filters as published, for example Scratch Tickets, Powerball, Lotto Texas, Pick 3. |
| `minPrize` | integer | no | (none) | Only count claims at or above this amount, for example 600 or 1000000. |
| `groupByGame` | boolean | no | `true` | One row per store and game. Turn off for one row per store. |
| `maxRetailers` | integer | no | `200` | Maximum number of retailer rows, largest prize total first. |

A working example to paste into the Input tab:

```json
{
  "minPrize": 10000,
  "groupByGame": false,
  "maxRetailers": 25
}
```

### Use cases

- Publish a list of Texas winning stores by prize total.
- Find stores where large prizes were sold with `largest_prize_usd`.
- Compare claim activity across cities and game categories.

### Coverage and freshness

Based on the Texas Lottery Commission winners list, updated daily. Only claims with a known selling retailer are counted.

### Pricing

This actor uses pay-per-event pricing. These are the current Apify prices, read on 2026-11-06.

| Event | Price | When it is charged |
|---|---|---|
| `result` | $0.015 | Each record delivered to your dataset |
| `apify-actor-start` | $0.003 | When a run starts, once per GB of run memory with a minimum of one |

At the default 512 MB, a run that delivers 100 records costs $1.503.

- Apify asks for a maximum spend of at least $0.018 per run on this actor.
- Accounts on the free Apify plan receive up to 10 results per run.
- If nothing matches or the source fails, you get one row with an `error` field and no `result` charge. The start event still applies to the run.
- Set a maximum cost per run and the actor stops delivering results when it reaches that limit.

### Comparison with other Apify actors

No dedicated actor for this source on the Apify Store as of November 2026. We searched the public Store on 2026-11-06 with queries including "texas lottery retailer" and "texas lottery winners", and we reviewed the listings for this source and data type. Store listings change, so run the same search before you rely on this.

### Related JackpotLedger actors

Other public JackpotLedger actors for the same buyer:

- [Texas Lottery Results: Pick 3, Daily 4, Cash Five & More](https://apify.com/jackpotledger/texas-lottery-draw-results): lottery draw results for Texas
- [Texas Scratch-Off Prizes Remaining & Odds](https://apify.com/jackpotledger/texas-scratch-off-prizes-remaining): scratch-off prize data for Texas
- [Top Lottery Stores Ranking: Best-Selling & Winning Stores](https://apify.com/jackpotledger/lucky-lottery-stores-ranking): lottery retailer data across states
- [New Scratch-Off Games Feed: New Tickets by State](https://apify.com/jackpotledger/new-scratch-off-games-feed): scratch-off prize data across states

### FAQ

**Are player names included?**

No. Only totals per store are returned.

**What can I filter by?**

The input accepts `dateFrom`, `dateTo`, `retailerNames`, `retailerIds`, `cities`, `zipCodes`, `counties`, `gameCategories`, `minPrize` and `groupByGame`. The Input and filters section explains each one.

**Can I run it on a schedule?**

Yes. Create an Apify schedule for the actor, then send the dataset to your database, a spreadsheet or a webhook.

### Run it through the Apify API

Replace `<TOKEN>` with your Apify API token.

```bash
curl -X POST "https://api.apify.com/v2/acts/jackpotledger~texas-lottery-prize-claims-by-retailer/run-sync-get-dataset-items?token=<TOKEN>" \
  -H "Content-Type: application/json" \
  -d '{"minPrize": 10000, "groupByGame": false, "maxRetailers": 25}'
```

With the Apify CLI:

```bash
apify call jackpotledger/texas-lottery-prize-claims-by-retailer --input '{"minPrize": 10000, "groupByGame": false, "maxRetailers": 25}'
```

Every run writes to a dataset that you can export as JSON, CSV or Excel from the Storage tab or through the Apify API.

***

*JackpotLedger is an independent data provider and is not affiliated with any lottery, regulator or operator named on this page. Always confirm winning numbers and prize details with the official source.*

# Actor input Schema

## `dateFrom` (type: `string`):

First date to include, as YYYY-MM-DD. Leave empty for the last 30 days.

## `dateTo` (type: `string`):

Last date to include, as YYYY-MM-DD. Leave empty for today.

## `retailerNames` (type: `array`):

Optional partial-match filters on the store name, for example 7-ELEVEN.

## `retailerIds` (type: `array`):

Optional official retailer numbers.

## `cities` (type: `array`):

Optional city filters.

## `zipCodes` (type: `array`):

Optional 5-digit ZIP codes.

## `counties` (type: `array`):

Optional county filters.

## `gameCategories` (type: `array`):

Optional game filters as published, for example Scratch Tickets, Powerball, Lotto Texas, Pick 3.

## `minPrize` (type: `integer`):

Only count claims at or above this amount, for example 600 or 1000000.

## `groupByGame` (type: `boolean`):

One row per store and game. Turn off for one row per store.

## `maxRetailers` (type: `integer`):

Maximum number of retailer rows, largest prize total first.

## Actor input object example

```json
{
  "groupByGame": true,
  "maxRetailers": 200
}
```

# Actor output Schema

## `results` (type: `string`):

No description

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {};

// Run the Actor and wait for it to finish
const run = await client.actor("jackpotledger/texas-lottery-prize-claims-by-retailer").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {}

# Run the Actor and wait for it to finish
run = client.actor("jackpotledger/texas-lottery-prize-claims-by-retailer").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{}' |
apify call jackpotledger/texas-lottery-prize-claims-by-retailer --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,jackpotledger/texas-lottery-prize-claims-by-retailer"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/tveRQtTj38yFOvIDk/builds/7xPGqkeCPl3A7qMRR/openapi.json
