# Texas County Burn Ban Monitor (Texas A\&M Forest Service) (`texas-data-feeds/texas-burn-ban-monitor`) Actor

Daily list of Texas counties under a burn ban, with start date, days in effect and FIPS. Filter by county or new bans. Data from the Texas A\&M Forest Service public map.

- **URL**: https://apify.com/texas-data-feeds/texas-burn-ban-monitor.md
- **Developed by:** [Texas Data Feeds](https://apify.com/texas-data-feeds) (community)
- **Categories:** Developer tools, Lead generation, Open source
- **Security:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.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 County Burn Ban Monitor

Daily, structured list of **Texas counties under an outdoor burn ban** — county name, 5-digit FIPS, ban start date and days in effect — ready for spreadsheets, dashboards, alerts and integrations.

### Why use it

- Land-clearing, welding, construction and ag crews working across many counties
- Insurers, utilities, ranches and event planners checking fire restrictions
- Pair with our **Texas Drought & Water Restrictions** actor for a full Texas drought picture

### Input

| Field | Meaning |
|---|---|
| `counties` | Limit to these counties (empty = all 254) |
| `onlyActive` | Only counties with a ban in effect (default on) |
| `startedWithinDays` | Only bans started in the last N days — schedule daily for "new ban" alerts |
| `maxItems` | Cap results |

### Output (one item per county)

`county`, `county_fips`, `burn_ban_active`, `ban_start_date`, `days_in_effect`, `source_url`, `data_url`, `scraped_at`.

### Pricing

Pay per event: a small fee per run start plus a fraction of a cent per county returned.

### Source & credit

Data comes from the **Texas A\&M Forest Service** public burn-ban map ([free info page](https://tfsweb.tamu.edu/wildfire-and-other-disasters/burn-bans-and-information/)). TAMFS provides the map as a public service; **county commissioners court orders are the official source** of burn-ban status. We fetch politely (one request per run).

### Disclaimer

Not affiliated with or endorsed by Texas A\&M Forest Service, Texas A\&M University or any Texas county. Data is provided "as is", without warranty of any kind; it may be delayed or incomplete. Always confirm with your county before burning.

# Actor input Schema

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

Texas county names to include (e.g. Bexar). Empty = all 254 counties.

## `onlyActive` (type: `boolean`):

If on, return only counties currently under a burn ban.

## `startedWithinDays` (type: `integer`):

Only bans that started in the last N days, for new-ban alerts.

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

Cap on results.

## `requestDelaySecs` (type: `integer`):

Polite delay between requests.

## Actor input object example

```json
{
  "counties": [],
  "onlyActive": true,
  "startedWithinDays": 0,
  "maxItems": 0,
  "requestDelaySecs": 2
}
```

# Actor output Schema

## `dataset` (type: `string`):

Dataset with all county records

# 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("texas-data-feeds/texas-burn-ban-monitor").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("texas-data-feeds/texas-burn-ban-monitor").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 texas-data-feeds/texas-burn-ban-monitor --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,texas-data-feeds/texas-burn-ban-monitor"
        }
    }
}
```

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/6b4SZYi91tWReKcQn/builds/pqgSpwWPbdi0Cv1Fq/openapi.json