Schema Endpoints

The schema endpoints return field definitions for each of Regrid's data products. Use these endpoints to programmatically discover available fields, data types, and descriptions for any dataset — useful for building dynamic integrations, validating field names, or generating documentation automatically. All schema endpoints require a valid API token and return a JSON object describing the fields in that schema.

• Base URL: https://app.regrid.com/api/v2
• Required parameter (all endpoints): token — your Regrid API authorization token.

Parcel Schema

GET /schemas/parcel Returns the full field schema for Regrid's US parcel dataset. This is the primary reference for all standard field names, data types, and descriptions available in parcel API responses. Use this endpoint to discover what fields are available, understand their data types, and build field-aware integrations without hardcoding field names.

This endpoint retrieves the current Regrid Parcel Schema. You can use premium_only to retrieve the schema listed for only premium fields.

• premium_only: Default returns all. Set to true to return schema for only premium fields and false to return only Standard fields. US schema only.

Example request GET https://app.regrid.com/api/v2/schemas/parcel?token=<token>

Matched Building Footprint

GET /schemas/building

Returns the field schema for building footprint data matched to parcels. Includes geometry, square footage, and structure attributes sourced from national building footprint datasets. Use this to understand the fields returned when return_matched_buildings=true is set on parcel queries.

Example request GET https://app.regrid.com/api/v2/schemas/building?token=<token>

Matched Secondary Addresses

GET /schemas/address

Returns the field schema for secondary address records matched to parcels, such as unit-level addresses within multi-family or commercial buildings. Use this to understand the structure of the address records returned when return_matched_addresses=true is set on parcel queries.

Example request GET https://app.regrid.com/api/v2/schemas/address?token=<token>

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. Use this to understand the fields returned when return_enhanced_ownership=true is set on parcel queries.

Example request GET https://app.regrid.com/api/v2/schemas/enhanced_ownership?token=<token>

Standardized Zoning

GET /schemas/zoning

Returns the field schema for standardized zoning data joined to parcels. Includes zoning code, classification, and permitted use attributes normalized across jurisdictions. Use this to understand the fields returned when return_zoning=true is set on parcel queries.

Example request GET https://app.regrid.com/api/v2/schemas/zoning?token=<token>

Global Parcel Schema

GET /schemas/ca or GET /schemas/fr (depending on the desired country).

Returns the full field schema for Regrid's Canada and Europe parcel datasets. Field names, data types, and descriptions follow international parcel and assessor data conventions, which differ from the US parcel schema in several areas including the use of admin0, admin1, admin2, and admin3 in place of US-specific geographic fields. Use this endpoint when building integrations against Canadian and European parcel data. A list of

Example request GET https://app.regrid.com/api/v2/schemas/ee?token=<token>