# Texas Data Breach Reports Scraper (`defenestrator/texas-data-breach-reports`) Actor

Scrape the official public Texas Attorney General Data Security Breach Reports listing into structured rows for compliance monitoring, cybersecurity research, and public-record analysis. Unofficial; not affiliated with the Texas Attorney General or State of Texas.

- **URL**: https://apify.com/defenestrator/texas-data-breach-reports.md
- **Developed by:** [Defenestrator](https://apify.com/defenestrator) (community)
- **Categories:** Business, News
- **Stats:** 1 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $4.00 / 1,000 texas data breach report rows

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/platform/actors/running/actors-in-store#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
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.
Actors are written with capital "A".

## 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.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## Texas Data Breach Reports Scraper

Export the official Texas Attorney General public **Data Security Breach Reports** listing into structured, source-linked dataset rows for compliance monitoring, cybersecurity research, public-record analysis, and lawful business research.

Use this Actor when you need a repeatable Apify dataset/API output instead of manually searching the public Texas OAG breach-report listing.

**Unofficial / not affiliated:** this Actor is independently developed and is not affiliated with, endorsed by, sponsored by, or maintained by the Texas Attorney General or the State of Texas.

### Why this data matters

Texas law requires businesses and organizations that experience a data breach affecting 250 or more Texans to report that breach to the Texas Attorney General. The OAG publishes a public listing of those reports. This Actor turns that listing into filterable rows you can schedule, download, or feed into internal monitoring workflows.

The official listing notes that details, including affected counts and notice status, may change after a report is listed. Always verify important decisions against the official OAG source.

### Common use cases

- Monitor newly published Texas breach reports.
- Track larger reported breaches by affected Texans.
- Filter reports by entity name, information type, date range, or notice status.
- Support cybersecurity, compliance, insurance, incident-response, journalism, or public-record research.
- Export the Texas OAG public breach listing to JSON, CSV, Excel, or an API integration.

### What you get

Each dataset row can include:

- report ID
- entity or individual name as published by the source
- entity type
- address/city/state/ZIP when published by the source
- types of personal information affected
- number of Texans affected
- whether notice was provided to consumers
- notice methods
- breach start/end/discovery dates
- publication date at the OAG website
- source URL

### Example output

```json
{
  "reportId": "BR-0004052",
  "entityName": "American National Bank & Trust",
  "entityType": "Financial Services",
  "publishedAt": "2025-01-16",
  "breachStartDate": "2024-09-18",
  "breachEndDate": "2024-09-20",
  "texansAffected": 2368,
  "noticeProvided": true,
  "noticeMethods": ["U.S. Mail"],
  "informationTypes": ["Name of individual", "Address", "Social Security Number Information"]
}
```

### Input filters

| Field | Description |
|---|---|
| `maxItems` | Maximum matching rows to save. |
| `publishedFrom` / `publishedTo` | Inclusive publication date bounds, `YYYY-MM-DD`. |
| `entityNameQuery` | Case-insensitive entity-name search. |
| `informationTypeQuery` | Search affected information types such as `Social Security`, `Driver`, `Medical`, or `Financial`. |
| `minTexansAffected` | Only include reports at or above a threshold. |
| `includeAllVersions` | Request all available versions from the public listing instead of the default current listing. |
| `sortBy` / `sortDescending` | Output ordering before `maxItems` truncation. |

### Example input

```json
{
  "maxItems": 25,
  "publishedFrom": "2025-01-01",
  "minTexansAffected": 1000,
  "sortBy": "publishedAt",
  "sortDescending": true
}
```

### Pricing

from $4.00 / 1,000 Texas data breach report rows

This Actor uses Apify Pay per Event pricing with platform usage included. The row event is charged only for useful rows written to the default dataset.

| Event | Price | Unit |
|---|---:|---|
| Actor start (`apify-actor-start`) | `$0.00005` | Once when the run starts. |
| Texas data breach report row (`apify-default-dataset-item`) | `$0.004` | Per Texas data breach report row. |

A row is one normalized Texas OAG data breach report row. Apify plan discounts, user-configured max-charge limits, and any future Apify pricing UI changes may affect final charges.

### Official source

- Texas OAG Data Security Breach Reports: https://oag.my.site.com/datasecuritybreachreport/apex/DataSecurityReportsPage

### Limitations and responsible use

This Actor does not submit breach reports, access non-public records, determine legal obligations, or provide legal advice. It only extracts the public listing made available by the Texas Attorney General.

Do not use this Actor as the sole basis for legal, compliance, credit, employment, insurance, eligibility, or consumer-impact decisions. Use the data lawfully, respect applicable privacy and communications laws, and do not use it for unsolicited mass messaging, harassment, or unlawful activity.

### Related Actors in this portfolio

This Actor is part of the **Public risk and enforcement monitors** group. These are narrow, source-specific Apify Actors intended for scheduled checks and repeatable dataset exports — not broad scraped-content feeds.

- [Texas Data Breach Reports Scraper](https://apify.com/defenestrator/texas-data-breach-reports) — Official Texas data-breach notice rows for cybersecurity/compliance monitoring.
- [OSHA Severe Injury Reports Scraper](https://apify.com/defenestrator/osha-severe-injury-reports) — Official OSHA severe-injury report rows for workplace-safety research.
- [CFPB Enforcement Actions Monitor](https://apify.com/defenestrator/cfpb-enforcement-actions-monitor) — Official CFPB enforcement-action rows for financial regulatory monitoring.
- [PHMSA Pipeline Enforcement Cases](https://apify.com/defenestrator/phmsa-pipeline-enforcement-cases) — Official PHMSA pipeline enforcement case rows for safety/compliance monitoring.

Each listing includes its own source notes, limits, pricing, and responsible-use caveats. Use the official source links in each Actor when decisions require verification.

# Actor input Schema

## `maxItems` (type: `integer`):

Maximum number of matching Texas OAG data security breach report rows to save.

## `publishedFrom` (type: `string`):

Optional inclusive published date lower bound in YYYY-MM-DD format.

## `publishedTo` (type: `string`):

Optional inclusive published date upper bound in YYYY-MM-DD format.

## `entityNameQuery` (type: `string`):

Optional case-insensitive filter applied to the entity or individual name.

## `informationTypeQuery` (type: `string`):

Optional case-insensitive filter applied to affected information types, such as Social Security, Driver, Medical, Financial, or Health Insurance.

## `minTexansAffected` (type: `integer`):

Only include reports where the number of affected Texans is at least this value.

## `includeAllVersions` (type: `boolean`):

Ask the Texas OAG public listing for all available versions instead of the default current listing. Leave off unless you need historical/superseded versions.

## `sortBy` (type: `string`):

Field used before truncating to the maximum number of rows.

## `sortDescending` (type: `boolean`):

Sort newest/largest/Z-A first. Turn off for oldest/smallest/A-Z first.

## `includeRawFields` (type: `boolean`):

Include selected raw source field names for debugging/source reconciliation.

## `timeoutSecs` (type: `integer`):

HTTP timeout per request to the official public Texas OAG listing.

## Actor input object example

```json
{
  "maxItems": 500,
  "publishedFrom": "2026-01-01",
  "minTexansAffected": 0,
  "includeAllVersions": false,
  "sortBy": "publishedAt",
  "sortDescending": true,
  "includeRawFields": false,
  "timeoutSecs": 30
}
```

# Actor output Schema

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

No description

## `summary` (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 = {
    "publishedFrom": "2026-01-01"
};

// Run the Actor and wait for it to finish
const run = await client.actor("defenestrator/texas-data-breach-reports").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 = { "publishedFrom": "2026-01-01" }

# Run the Actor and wait for it to finish
run = client.actor("defenestrator/texas-data-breach-reports").call(run_input=run_input)

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

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

```

## CLI example

```bash
echo '{
  "publishedFrom": "2026-01-01"
}' |
apify call defenestrator/texas-data-breach-reports --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "command": "npx",
            "args": [
                "mcp-remote",
                "https://mcp.apify.com/?tools=defenestrator/texas-data-breach-reports",
                "--header",
                "Authorization: Bearer <YOUR_API_TOKEN>"
            ]
        }
    }
}

```

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/yIJHtVVIBBIdLw2jK/builds/GQ571Veiqpir7pxNn/openapi.json