Documentation menu
Make the first call
Public property records and land-use rules for U.S. real estate, traced to their public sources.
One base URL and one header. Public operations take no credential; metered ones expect an API key in X-API-Key. Pass a location as a parameter: there is no separate resolve step, so your first call is the one that answers your question.
http://localhost:8000
- Paths
- 99
- Operations
- 116
- Groups in the reference
- 10
- Component schemas
- 317
Example request
curl -X GET 'http://localhost:8000/place?as_of=2026-09-13&address=100+Main+St&point=35.225%2C-78.642' \
-H 'X-API-Key: $PLACESTACK_API_KEY'How the API is shaped
A public property-record and land-use rules API for U.S. real estate: public property records, and what each jurisdiction allows, requires, has decided and is about to change about building on land. Every record traces to its public source, and every rule quotes the ordinance and says when it took effect.
How the paths are organized
- Ask about a place:
/place,/rule,/conformance,/parcel. A location is a parameter set - (
address,point=lat,lon,geometryplusbuffer,parcel,apnplusfips,plss, -
location_token), never a separate resolve step. - Public property records:
/property(assessment, tax, ownership and structures embedded) and -
/transaction(recorded sales, transfers and mortgages). Public sources only; an undisclosed value - is
withheld, never estimated. - Browse one town by its own names:
/jurisdiction/{id}/district/{code},/code/{kind}, -
/plan,/process/{type}. - Search across towns:
/permission,/ordinance,/section,/moratorium,/case, -
/permit,/meeting,/metric,/change_event,/coverage. Each takes one scope: -
region,jurisdiction(repeatable),state,county, orgeometryplusbuffer. - Reference by id:
/citation/{id},/document/{id},/answer/{id}.
Paths are singular nouns with no verbs. A relationship is a query parameter or an embedded array, never a nested path of peers. Leaf records (fees, votes, conditions, provenance, district shares) are embedded in the resource they belong to rather than served on their own.
Time
as_of is valid time, the law in force then. known_as_of is knowledge time, the answer we would have given then. Both default to now and both work identically everywhere. An interval as_of returns segment[], the maximal sub-intervals over which each fact was constant, never a winner.
Coverage
Every answer about law carries a coverage block saying what is held for the jurisdiction and layer it answered from, and how fresh it is. A fact's status distinguishes stated, conflicting and withheld. 404 means no such id and nothing else.
Collections, filters, errors
Cursor pagination only (cursor, size, total=true on the first page). sort=field or sort=-field. filter[<field>][<op>]=<value>; a row a filter cannot evaluate is returned as indeterminate, never silently dropped. Refusals are {"detail": {"error": {"code", "field", "detail", "message", "message_title"}}} with a code from GET /vocabulary/error_code. Mutations accept Idempotency-Key; updates require If-Match.
Common first calls
Each of these links into the group page that documents it in full.
/placeWhat is at a location, and who governs it
/ruleThe zoning rules at a location, as of a date, every number cited
/ruleThe same answer for up to 500 locations
/permissionWhere a use is allowed, across jurisdictions
/coverageWhat we cover, per jurisdiction per layer, including what we do not
/extractYour extracts
The reference, by group
Every operation, with its parameters, its responses and an example. Pick the group you need.
- Ask about a place
- 10 operations: place, rule, conformance, parcel.
- Public property records
- 4 operations: property, transaction.
- Jurisdictions and their law
- 14 operations: jurisdiction, district, code, process, region.
- Search across jurisdictions
- 7 operations: permission, ordinance, section, moratorium.
- What actually happens
- 7 operations: meeting, case, permit, metric.
- Evidence
- 9 operations: citation, document, answer.
- Change and coverage
- 16 operations: change_event, alert, webhook, coverage.
- Bulk, maps and research
- 19 operations: extract, map, ogc, inquiry.
- Reference
- 4 operations: vocabulary, service.
- Account
- 26 operations: identity, onboarding, auth, entitlement, usage, billing, oauth.
Conventions
These hold for all 116 operations. For what a field means rather than how to ask for it, see Concepts.
- Authentication
- Which credential each operation accepts, and where to get one.
- Errors
- The refusal shape, and what each status code means here.
- Pagination and cursors
- Walking a collection without missing or repeating a row.
- Filtering, sorting and fields
- Narrowing an answer, ordering it, and asking for less of it.
- Rate limits and quota
- The three refusals, and pricing a call before you make it.