API Endpoint Overview
Regrid’s API endpoints are organized by how you want to find data. All endpoints return standardized GeoJSON objects, making it easy to integrate parcel boundaries and property attributes into your maps and applications
đź“Ť Search by Location
| Name | Endpoint | Description |
|---|---|---|
| Point Lookup | GET & POST /api/v2/parcels/point | Returns parcel records at or near a given geographic coordinate. This is the most direct lookup method when you have a lat/lon — for example from a GPS reading, a map click, a device location, or a geocoded address — and want to find the parcel(s) that contain or are nearest to that point. |
| Address Lookup | GET /api/v2/parcels/address | Returns parcel records matching a street address within the United States and Puerto Rico. This is the right endpoint when you have a human-readable address and want to look up the corresponding parcel record — for example, in a property lookup tool, a real estate application, or a data enrichment pipeline. |
| APN Lookup | GET /api/v2/parcels/apn | Returns parcel records matching a given Assessor Parcel Number (APN) — the unique identifier assigned to each parcel by the local county assessor's office. This is the most authoritative lookup method when working with data sourced directly from county records, title documents, tax filings, or legal descriptions, where the APN is already known |
| Owner Name Lookup | GET /api/v2/parcels/owner | Returns all parcel records associated with a given owner name — either an individual or a business entity. This endpoint is useful for finding every property held by a specific person or organization, making it well-suited for ownership research, portfolio analysis, due diligence, and investigative workflows. |
| Search by Geometry | GET/POST /api/v2/parcels/area | Returns all parcels that fall within a specified geographic area, defined as a GeoJSON geometry. This is the right endpoint when you need to find every parcel inside a custom-drawn boundary — such as a neighborhood, a flood zone, a city block, or any arbitrary polygon — rather than searching by a single point or identifier. |
| Typeahead/autocomplete search | GET /parcels/typeahead | Provides real-time address suggestions as a user types, returning matching parcel records with their validated addresses and unique identifiers. This endpoint is purpose-built for powering address search inputs in applications — send each keystroke (or debounced input) and receive a ranked list of matching parcels to display as suggestions. |
| Parcel path lookup | GET /parcels/path | Returns the full record for a single parcel identified by its Regrid canonical path — a human-readable hierarchical identifier that encodes the parcel's location in the format /country/state/county/neighborhood/parcel-id (e.g., /us/tx/dallas/northeast-dallas/6471). |
| Lookup by Regrid ID | GET /parcels/{ll_uuid} | Returns the full record for a single parcel identified by its Regrid UUID (ll_uuid) — a globally unique, persistent identifier assigned to every parcel in the Regrid dataset. This is the most direct and reliable way to retrieve a specific parcel when you already have its ID stored. |
🛠️ The "Swiss Army Knife": Query by Fields
| Name | Endpoint | Description |
|---|---|---|
| Query By Fields | GET/POST /api/v2/parcels/query | This is our most powerful endpoint. It allows you to filter the entire nationwide dataset by any of the indexed schema attributes (e.g., land use, owner name, sales price) combined with a geometry filter (like a polygon)
|
Schemas
| Name | Endpoint | Description |
|---|---|---|
| Parcel Schema | GET /schemas/parcel | Returns the full field schema for Regrid's US parcel dataset, including field names, data types, and descriptions for all standard and enrichment columns. |
| Matched Building Footprint | GET /schemas/building | Returns the field schema for building footprint data matched to parcels, including geometry, square footage, and structure attributes sourced from national building footprint datasets. |
| Matched Secondary Addresses | GET /schemas/address | Returns the field schema for secondary address records matched to parcels, such as unit-level addresses within a multi-family or commercial building. |
| Enhanced Ownership | GET /schemas/enhanced_ownership | Returns the field schema for Regrid's enhanced ownership dataset, which provides additional owner name, mailing address, and entity-type fields beyond what county assessors supply. |
| Standardized Zoning | GET /schemas/zoning | Returns the field schema for standardized zoning data joined to parcels, including zoning code, classification, and permitted use attributes normalized across jurisdictions. |
| Canada Parcel Schema | GET /schemas/ca | Returns the full field schema for Regrid's Canada parcel dataset, including field names, data types, and descriptions specific to Canadian parcel and assessor data conventions. |
Metadata
| Name | Endpoint | Description |
|---|---|---|
| Verse Table | GET /verse | Returns Regrid's verse table, a county-level metadata table listing every county in the dataset along with coverage status, last refresh date, parcel count, and available data products for each geography. |
| Usage | GET /usage | Returns a summary of your current API usage, including parcel lookups and downloads consumed against your plan limits for the current billing period. |
| Detailed Usage | GET /usage/detailed | Returns a granular breakdown of your API usage by endpoint, date, and query type, useful for auditing consumption and understanding which requests are driving usage. |
| Report an Issue | POST /report | Submit a data quality report for a specific parcel, flagging incorrect attributes, geometry errors, or missing data so Regrid's team can review and correct the record. |
Global Endpoints
| Name | Endpoint | Description |
|---|---|---|
| Parcel Lookup for International Parcels | GET/POST /{country}/parcels/point | Returns the parcel or parcels at a given latitude/longitude coordinate for the specified country. Accepts a point geometry and returns all matching parcel records with their attributes and boundary. |
| Area Geometry Search for International Parcels | GET/POST /{country}/parcels/area | Returns all parcels that intersect or fall within a given polygon boundary for the specified country. Useful for bulk retrieval of parcels within a custom geographic area such as a neighborhood, district, or bounding box. |
| Address Search for International Parcels | GET /{country}/parcels/address | Returns parcels matching a given address string for the specified country. Performs address parsing and matching against parcel situs address records to return the most relevant result. |
| Regrid ID Lookup for International Parcels | GET /{country}/parcels/{ll_uuid} | Returns a single parcel record by its Regrid-assigned ll_uuid for the specified country. Use this endpoint to retrieve a known parcel directly using Regrid's stable unique identifier. |
| Assessor Parcel Number (APN) for International Parcels | GET /{country}/parcels/apn | Returns parcels matching a given assessor parcel number (APN) for the specified country. Searches across primary and alternative parcel number fields to find the best match. |
| Query by Field for International Parcels | GET /{country}/parcels/query | Returns parcels matching a custom field-value query for the specified country. Allows filtering parcel records by any supported schema field, enabling flexible attribute-based searches. |
| Parcel Path for International Parcels | GET /{country}/parcels/path | Returns a parcel record by its Regrid human-readable path for the specified country. The path follows Regrid's hierarchical geographic structure and can be used as a readable alternative to the ll_uuid for known parcels. |
Updated 3 months ago
Did this page help you?