CT ForeclosureDOCKET
COMMERCIAL DATA API

Build on a clearer record.

Synchronize the eligible Connecticut foreclosure database, then keep it current with observed changes.

API credentials require a Data API or Combined subscription. Requests run against the same eligible records as the dashboard.

Authenticate

Create a key in Account settings. Send it as a Bearer token. Store it on your server, never in public browser code.

curl https://YOUR_DOMAIN/v1/cases \
  -H "Authorization: Bearer YOUR_API_KEY"

Endpoints

GET /v1/cases

List records. Filter with q, town, type, status, or stage. Request up to 100 records per page and follow the returned cursor.

GET /v1/cases/{id}

Retrieve one eligible case by its stable identifier.

GET /v1/changes

Retrieve additions, updates, and removals. Persist the returned cursor. Cursors expire after 90 days; then repeat the initial sync.

GET /v1/coverage

Inspect available coverage and source freshness.

Synchronization

  1. Request the first case page and save its changesCursor watermark before processing the listing.
  2. Page through all cases and upsert records by ID.
  3. Replay changes from your starting cursor, including removal events.
  4. Continue daily. Remove records when a removal event arrives.

Limits & errors

10,000 requests per billing month; 60 per minute per account. A 429 response indicates an exhausted allowance. Back off on temporary 503 errors; failed service responses do not consume the monthly allowance.

401: invalid key. 402: subscription required. 404: record unavailable. 410: expired changes cursor. Do not interpret a failed request as an empty dataset.

OpenAPI specification

Permitted use

Internal business research and integration. Customer-facing redistribution and resale are excluded. Source records can be incomplete, delayed, or corrected; preserve their provenance in your workflow.