Texas HOA management certificates

At a glance

Publisher

Texas Real Estate Commission (TREC)

Jurisdiction

US-TX / Texas

Publisher updates

Updated daily by TREC

SourceFinch checks

Daily by default

Records per run

100 in the latest run

Record key

certificate_url

Acquired from

Open data portal: https://data.texas.gov/resource/8auc-hzdi.json?$select=name,county,city,zip,type,certificate&$order=certificate%20DESC&$limit=100

Recipe

v1.0.0, approved October 3, 2026

Verified since

October 3, 2026

Last green run

October 3, 2026

What the data contains

Texas requires every property owners' association to file a management certificate with the county and, since 2022, with the Texas Real Estate Commission (TREC), which publishes the statewide list as the TREC HOA Management Certificates dataset on the Texas Open Data Portal. Every row is a community association: POA for property owners' associations and COA for condominium associations. Each run asks the portal's SODA API for the 100 most recently recorded certificates (ordered by the certificate document link, whose path carries TREC's increasing record number) and returns one record per certificate with the association name, county, city, ZIP code, association type and a link to the filed certificate PDF. A monitor therefore reports newly registered associations and re-filed certificates. Only the columns listed here are requested; the certificate PDFs themselves are not read, and the dataset publishes no officer or homeowner contact columns. TREC refreshes the dataset daily. Some rows carry the state code in the county column as filed.

Fields and types

Every record has these fields. The key field certificate_url identifies a record across runs, so changes are reported field by field.

Sample output

The first 5 of 100 records from SourceFinch's own run on October 3, 2026, exactly as delivered.

[
  {
    "zip": "75165",
    "city": "Waxahachie",
    "name": "Buffalo Ridge Homeowners Association",
    "county": "Ellis",
    "certificate_url": "https://www.hoa.texas.gov/sites/default/files/certificates/199987/4591-6070/mc/Signed%20Buffalo%20Ridge%20Mgt%20Cert.pdf",
    "association_type": "POA"
  },
  {
    "zip": "77354",
    "city": "Magnolia",
    "name": "Westwood Landowners' Association",
    "county": "Montgomery",
    "certificate_url": "https://www.hoa.texas.gov/sites/default/files/certificates/199985/9377-12617/mc/Management%20Certificate%20filed.pdf",
    "association_type": "POA"
  },
  {
    "zip": "77840",
    "city": "College Station",
    "name": "North Country Estates Homeowners Association, Inc.",
    "county": "Brazos",
    "certificate_url": "https://www.hoa.texas.gov/sites/default/files/certificates/199984/13024-21641/mc/NORTH%20COUNTRY%20ESTATES%20HOA%20MGMT%20CERT-001.pdf",
    "association_type": "POA"
  },
  {
    "zip": "78295",
    "city": "San Antonio",
    "name": "Ridge at Deer Creek",
    "county": "TX",
    "certificate_url": "https://www.hoa.texas.gov/sites/default/files/certificates/199983/1278-35446/mc/Notice%20Homeowners%20Association%20for%20Deer%20Crest,%20The%20Ridge%20at%20Deer%20Creek%20and%20The%20Estates%20of%20Deer%20Creek,%20Inc.%20Amended%20Management%20Cer.pdf",
    "association_type": "POA"
  },
  {
    "zip": "77494",
    "city": "Katy",
    "name": "Regents Village Property Owners Association, Inc.",
    "county": "TX",
    "certificate_url": "https://www.hoa.texas.gov/sites/default/files/certificates/199980/4775-6288/mc/Regents%20Village%20-%20Management%20Certificate%202021.pdf",
    "association_type": "POA"
  }
]

Evidence behind every value

• Each run keeps the publisher's exact response, hashed with SHA-256. This sample came from a response with hash f2ce14d8e3b9d192078da37042262ac5c9738b4f98fb1bd460dadd3e90bcfcad.
• Every value records where it came from in that response: a JSON Pointer into the retained capture.
• Each run gets a signed manifest (Ed25519) timestamped by an RFC 3161 authority: this run's manifest hash is 4d960f5bce575bb7ef3dcca9f341371582ca76aad70953bb5ca5b1d4efc73248, timestamped October 3, 2026.
• The compliance state at capture is recorded with the evidence: robots.txt hash and verdict, AI-preference signals, crawler identity and the usage rights below.
• Download any run as an evidence bundle (WACZ) and check it offline, without trusting SourceFinch: sourcefinch verify-bundle run.wacz.

Terms posture and usage rights

The Texas Open Data Portal publishes the TREC dataset for public use through Socrata's anonymous SODA API; no key or registration is needed for moderate use and the portal's robots.txt asks for a 1 second crawl delay, which SourceFinch honours. The dataset carries no separate licence; the portal links Tyler Technologies' (Socrata) terms of service, which do not restrict reuse of agency data. Management certificates are public filings under Texas Property Code 209.004.

Source: Texas Real Estate Commission, TREC HOA Management Certificates (Texas Open Data Portal).

Usage rights travel with every record SourceFinch delivers (API, exports, webhooks and evidence bundles). They are our documented understanding of the publisher's stated terms, not legal advice.

Reliability

Runs, last 30 days

0

Green

—

Failed

0

Median run time

—

Latest run

success, October 3, 2026

Measured on runs of this recipe version across SourceFinch, anonymized. This recipe is newly Verified; the numbers fill in as it runs daily.

Use it

Every surface creates the same monitor from this Verified recipe. Monitors keep record history, report field-level changes and deliver by webhook, export or email. You confirm you have the right to collect the source (rights: true).

{
  "name": "Texas HOA management certificates",
  "url": "https://data.texas.gov/resource/8auc-hzdi.json?$select=name,county,city,zip,type,certificate&$order=certificate%20DESC&$limit=100",
  "recipe": {
    "mode": "http",
    "format": "json",
    "items": "[*]",
    "fields": {
      "zip": "zip",
      "city": "city",
      "name": "name",
      "county": "county",
      "certificate_url": "certificate.url",
      "association_type": "type"
    },
    "required": [
      "certificate_url",
      "name"
    ]
  },
  "key_field": "certificate_url",
  "schedule": "daily",
  "rights": true
}

# the Verified entry (fields, recipe, sample, terms) as JSON
curl https://sourcefinch.com/v1/catalog/texas-hoa-management-certificates -H "Authorization: Bearer $SOURCEFINCH_API_KEY"

# create the monitor from source.json (below)
curl -X POST https://sourcefinch.com/v1/sources \
  -H "Authorization: Bearer $SOURCEFINCH_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: $(uuidgen)" \
  -d @source.json

# then run it now (later runs follow the schedule)
curl -X POST https://sourcefinch.com/v1/sources/$SOURCE_ID/runs \
  -H "Authorization: Bearer $SOURCEFINCH_API_KEY" \
  -H "Idempotency-Key: $(uuidgen)"

sourcefinch login
sourcefinch catalog get texas-hoa-management-certificates --source-json > source.json
sourcefinch sources create --file source.json
sourcefinch runs create $SOURCE_ID --wait
sourcefinch records $SOURCE_ID

import { SourceFinch } from "@tsg/sourcefinch";

const sf = new SourceFinch({ apiKey: process.env.SOURCEFINCH_API_KEY });
const entry = await sf.catalog.get("texas-hoa-management-certificates");
const source = await sf.sources.create({
  name: entry.name.slice(0, 100),
  url: entry.acquisition_path.endpoint,
  recipe: entry.recipe.definition,
  key_field: entry.recipe.key_field,
  schedule: entry.recipe.schedule,
  rights: true, // you confirm you have the right to collect this source
});
const run = await sf.runs.wait((await sf.runs.create(source.id)).id);
console.log(run.status);

claude mcp add --transport http sourcefinch https://sourcefinch.com/mcp

# then ask your agent:
"Use SourceFinch to monitor Texas HOA management certificates: get_catalog_source texas-hoa-management-certificates,
then create_source with its create_source_args (dry run first), then run_source."

Pricing

Each check is one run, whatever the number of records, and failed runs are free. On its default daily schedule this source uses about 30 runs a month, which fits the Free plan's 300 runs. It uses HTTP acquisition, so no browser runs are needed. See plans.

Related sources

• Baltimore County, Maryland community associations · Baltimore County, Maryland
• Colorado HOA and condominium association registrations · Colorado Department of State
• Connecticut HOA and condominium association registrations · Connecticut Secretary of the State
• Florida Statutes chapter 720 (homeowners' associations) sections · The Florida Legislature (Online Sunshine)