# Colorado Water Rights & Well Permits - DWR Registers (`j0401/co-water-rights`) Actor

Colorado DWR registers (public open data): 310k decreed water rights with decreed uses, priority dates, rate and location, plus 651k well permit applications with status, driller, depth and yield. A well's wdid keys the water right against it. Search by county, structure, source or status.

- **URL**: https://apify.com/j0401/co-water-rights.md
- **Developed by:** [Wenhao Yang](https://apify.com/j0401) (community)
- **Categories:** Business
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.03 / 1,000 colorado water records

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

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

## Colorado Water Rights & Well Permits - DWR Registers

Two registers from the Colorado Division of Water Resources, together: **310,858
decreed water rights** and **651,900 well permit applications**, joined on the
water-district identifier.

### Low cost

**From $0.00005 per record, down to $0.00003 at Gold.** Pay only for the records
you actually receive - the whole register stays queryable, you are never billed
for the scan behind it.

### Two corpora, one key

Pick a `corpus` and search it:

- **`rights`** (default) - every decreed water right: the ditch, well,
  reservoir, spring, pipeline or well field it sits on, the water source, the
  decreed uses, the appropriation and adjudication dates that fix its priority,
  the decreed rate and volumetric limit, the water court case, and the location.
- **`wells`** - every well permit application, from receipt through
  construction to abandonment: status, driller's permit, designated basin and
  management district, the physical completion (depth, perforated casing, yield
  in gpm, static water level) and the address.

A well permit carries a **`wdid`** that keys the water right decreed against it.
`mode=profile` with a `wdid` returns the right plus **every well linked to it** -
one exact join, no name matching.

### Filter it

- **County** - `county="DOUGLAS"` (case-insensitive).
- **Structure** - `structureType="Ditch"`, `"Reservoir"`, `"Spring"`.
- **Source** - `waterSource="LARAMIE"`, `"SOUTH PLATTE"`.
- **Where / district** - `division=1`, `waterDistrict=2`.
- **Well status** - `currentStatus="Well Constructed"`,
  `"Permit Issued"`, `"Well Abandoned"`, `"Permit Expired"`.
- **Physical** - `minDepth=500`, `minYield=100`.
- **Exact ids** - `wdid`, `receipt`, `permit`; `caseNo` matches a substring.

Note: `structureType` and `currentStatus` are matched **exactly**, so "Well"
does not also return "Well Field".

### Example inputs

**Every ditch in one county** - combine corpus and filters.

```json
{ "corpus": "rights", "county": "GARFIELD", "structureType": "Ditch", "maxResults": 25 }
```

**A senior right, and the wells on it** - the profile join.

```json
{ "corpus": "rights", "mode": "profile", "wdid": "0100753", "maxResults": 100 }
```

**Producing wells by status** - `corpus=wells`.

```json
{ "corpus": "wells", "currentStatus": "Well Constructed", "minYield": 500, "maxResults": 50 }
```

**Counts by structure** - `mode=aggregate`.

```json
{ "corpus": "rights", "mode": "aggregate", "groupBy": "structureType" }
```

### Or roll up a corpus

Set `mode=aggregate` and get a rolled-up count by a dimension of the chosen
corpus - **structure type**, **county**, **division**, **water district**,
**adjudication type** or **plan type** for rights; **status**, **county**,
**designated basin**, **management district**, **permit category** or
**location type** for wells. Every group comes back - this mode is not cut off
by `maxResults`.

### Example output

**One water right** - `corpus=rights`:

```json
{
 "platform": "co-water-rights",
 "corpus": "rights",
 "recordType": "waterRight",
 "mode": "rows",
 "wdid": "0110212",
 "waterRightName": "SMITH LFH WL FLD",
 "structureType": "Well Field",
 "waterSource": "LARAMIE FOX HILLS",
 "county": "DOUGLAS",
 "division": "1",
 "waterDistrict": "1",
 "appropriationDate": "2006-11-30",
 "adjudicationDate": "2006-12-31",
 "caseNo": "06CW0245",
 "maxDecreedRate": "",
 "totalVolumetricLimit": "9.9000"
}
```

**`mode=aggregate`, `groupBy=structureType`** - one count row per structure:

```
Well                92,889
Ditch               82,160
Reservoir           50,551
Spring              34,291
Well Field          16,227
Pipeline             9,035
```

### Notes on the data, from the source

- **The well -> right link is one-way and partial.** 80,293 of the 651,900 well
  rows (12.3%) carry a `wdid`; a right keys many wells or none, and most well
  rows predate the field. A `profile` returns the wells that actually resolved,
  not a claim that they are the only wells on the right.
- **These are historical registers, not live feeds.** A well permit's
  `permitIssued` reaches back decades. `modified` is the source's own edit
  stamp, and `sourceUpdatedAt` carries the newest one - the freshness signal an
  agent can read without running the actor.
- **`maxDecreedRate` and `totalVolumetricLimit` are only populated where the
  decree set them**, so blank is normal.
- **Counties are stored uppercase**, but the filter upper-cases what you pass,
  so a mixed-case county still matches.

# Actor input Schema

## `wdid` (type: `string`):

Exact WDID, e.g. '0100753'. Keys a water right and the wells linked to it.

## `waterRightName` (type: `string`):

Substring match on the decreed right's name.

## `structureType` (type: `string`):

Exact structure type, e.g. 'Ditch', 'Well', 'Reservoir', 'Spring'.

## `waterSource` (type: `string`):

Substring match on the source, e.g. 'LARAMIE', 'SOUTH PLATTE'.

## `county` (type: `string`):

Colorado county name (case-insensitive), e.g. 'DOUGLAS'.

## `division` (type: `integer`):

DWR division number (1-7).

## `waterDistrict` (type: `integer`):

DWR water district number.

## `caseNo` (type: `string`):

Substring match on the water court case number.

## `planType` (type: `string`):

Exact plan type code.

## `receipt` (type: `string`):

Exact DWR receipt number for a well application.

## `permit` (type: `string`):

Exact well permit number.

## `currentStatus` (type: `string`):

Exact well status, e.g. 'Well Constructed', 'Permit Issued', 'Well Abandoned'.

## `contactName` (type: `string`):

Substring match on the permit contact / owner name.

## `designatedBasin` (type: `string`):

Substring match on the designated groundwater basin.

## `associatedUses` (type: `string`):

Substring match on the permitted well uses.

## `associatedAquifers` (type: `string`):

Substring match on the aquifers the well draws from.

## `appropriatedFrom` (type: `string`):

Earliest appropriation date (rights), YYYY-MM-DD.

## `appropriatedTo` (type: `string`):

Latest appropriation date (rights), YYYY-MM-DD.

## `issuedFrom` (type: `string`):

Earliest well permit issued date, YYYY-MM-DD.

## `issuedTo` (type: `string`):

Latest well permit issued date, YYYY-MM-DD.

## `minRate` (type: `number`):

Smallest max decreed rate (rights).

## `maxRate` (type: `number`):

Largest max decreed rate (rights).

## `minVolume` (type: `number`):

Smallest total volumetric limit (rights).

## `maxVolume` (type: `number`):

Largest total volumetric limit (rights).

## `minDepth` (type: `number`):

Shallowest well depth (wells).

## `maxDepth` (type: `number`):

Deepest well depth (wells).

## `minYield` (type: `number`):

Smallest reported yield in gpm (wells).

## `maxYield` (type: `number`):

Largest reported yield in gpm (wells).

## `corpus` (type: `string`):

rights = decreed water rights (310k). wells = well permit applications (651k). Filters below apply to the corpus you pick.

## `mode` (type: `string`):

rows = records matching your filters. aggregate = one count row per group (see groupBy). profile = one water right plus every well linked to it (requires wdid).

## `groupBy` (type: `string`):

Aggregate by a dimension of the chosen corpus. Available keys differ per corpus (rights: structureType/county/division/; wells: currentStatus/county/).

## `maxResults` (type: `integer`):

Cap the number of records returned (0 = default 50). Records are charged individually; there is no per-run charge cap.

## Actor input object example

```json
{
  "wdid": "",
  "waterRightName": "",
  "structureType": "",
  "waterSource": "",
  "county": "",
  "caseNo": "",
  "planType": "",
  "receipt": "",
  "permit": "",
  "currentStatus": "",
  "contactName": "",
  "designatedBasin": "",
  "associatedUses": "",
  "associatedAquifers": "",
  "appropriatedFrom": "",
  "appropriatedTo": "",
  "issuedFrom": "",
  "issuedTo": "",
  "corpus": "rights",
  "mode": "rows",
  "groupBy": "",
  "maxResults": 50
}
```

# Actor output Schema

## `recordsUrl` (type: `string`):

Colorado Water Rights & Well Permits - DWR Registers records - as JSON

## `datasetUrl` (type: `string`):

No description

## `runUrl` (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("j0401/co-water-rights").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("j0401/co-water-rights").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 j0401/co-water-rights --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,j0401/co-water-rights"
        }
    }
}
```

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/z4FSFIT3LfuknEpUR/builds/be5HBOkME0Hr3gax1/openapi.json