PARCEL API version 0.55.0

PARCEL API documentation

US county property records as an API: parcels, owners, assessments, sales, photos and parcel boundaries for the counties we collect, in one schema across every county. Every customer route is under /v1 at https://13-140-33-19.sslip.io.

Developer guide

How the API works: keys and limits, the property id, paging, the change feed, map layers, sales, comps, images, errors.

API reference

Every customer route with its parameters, response shapes and examples.

Changelog

Every change a caller can see, newest first, as a page, as data and as a feed.

For agents

One screen of plain text: what PARCEL is, the one header, and the routes that answer most questions.

Your first call

Every request carries your API key in one header. Find a property by its street address:

curl -H "Authorization: Bearer $PARCEL_KEY" \
  "https://13-140-33-19.sslip.io/v1/parcels?q=109+Freeman+Dr+Warner+Robins+GA"

The answer's property_id (for example 13153-0W050J08B000) is the id to store: open the full record at GET /v1/parcels/{property_id}. The guide explains the id, and the reference lists every route.

Follow every change

The changelog is data as well as a page. Ask for what changed since the version you built against, or subscribe to the feed:

curl "https://13-140-33-19.sslip.io/changelog?since=0.26.0"
curl "https://13-140-33-19.sslip.io/changelog.atom"

Each version lists what was added, changed, deprecated, removed or fixed in the API, and what data was added. A breaking change is always named there, with how to move to the new form.

Every document

PathWhat it is
/developersthis page: the documentation home
/docs/guidethe developer guide, as a web page with a contents list
/docs/api.mdthe developer guide, as Markdown
/docsthe API reference (Swagger UI): every customer route, with try-it-out
/redocthe API reference (ReDoc), one long readable page
/openapi.jsonthe API reference as an OpenAPI 3 document, for code generators
/docs/changelogthe changelog, as a web page
/changelogthe changelog as JSON: one object a version, ?since= for what changed after
/changelog.mdthe changelog, as Markdown
/changelog.atomthe changelog as an Atom feed, for a feed reader or a script
/llms.txta one-screen plain-text index, for an agent deciding what to call

None of these needs a key. The routes they describe do: a call without one is answered 401.