qPublic Property Records APIqpublic.schneidercorp.com ↗
Search and retrieve property records from qPublic. Access owner info, valuations, building details, sales history, exemptions, and fees via 2 endpoints.
curl -X GET 'https://api.parse.bot/scraper/2a0208a7-8136-41b9-97e9-115f3fd57461/search_properties?address=E+MAIN+ST' \ -H 'X-API-Key: $PARSE_API_KEY'
Search for properties by address. Returns a list of matching properties with parcel ID, account number, owner, address, city, and legal description. If only one result is found, also returns full property details in a detail object.
| Param | Type | Description |
|---|---|---|
| addressrequired | string | Address to search for (e.g. '100 S MAIN ST', '1000 E MAIN ST') |
{
"type": "object",
"fields": {
"detail": "object (only present when single result) with full property details including summary, owners, valuations, buildings, land, sales, fees, exemptions, yard_items",
"properties": "array of property objects with parcel_id, account_number, owner, property_address, city, legal_description",
"total_results": "integer indicating the number of matching properties"
},
"sample": {
"data": {
"properties": [
{
"city": "CAMPOBELLO",
"owner": "PEACH COUNTRY HOLDINGS LLC",
"parcel_id": "1-26-04-012.00",
"account_number": "7932",
"property_address": "100 N MAIN ST",
"legal_description": "LOTS 1, 2 & 3 E R PERRY JR ESTATE PB 89-240"
}
],
"total_results": 8
},
"status": "success"
}
}About the qPublic Property Records API
The qPublic Property Records API provides access to county-level property data through 2 endpoints: search_properties and get_property_details. A single parcel lookup returns over 30 structured fields covering owner information, multi-year valuations, building characteristics, land records, sales history, tax exemptions, and fees — sourced from qPublic's database of assessor records maintained by Schneider Corporation.
Endpoints
The API exposes two endpoints. search_properties accepts an address string and returns a list of matching parcels, each with parcel_id, account_number, owner, property_address, city, and legal_description. When the search resolves to exactly one result, the response also includes a detail object containing the full property record — useful when you already know the address and want to avoid a second round-trip.
get_property_details accepts a parcel_id (e.g. 7-13-01-001.02) and returns the complete record for that parcel. Key response objects include summary (parcel metadata such as millage group, utilities, fire district, and site conditions), owners (mailing address components), and valuations (keyed by year, with market land value, market improvement value, total market value, and taxable values across multiple assessment years).
Property Characteristics
The buildings array describes each structure on a parcel with fields like Style, Gross Sq Ft, Year Built, Condition, and an areas breakdown. The land array includes land use classification, unit count, unit type, frontage, and depth. yard_items covers ancillary structures or improvements with description, year built, size, and quantity.
Tax and Transaction Data
The sales array contains transaction history per parcel: sale date, sale price, instrument number, deed book, deed page, grantor, and grantee. The exemptions array lists applicable tax exemptions, and fees records assessment charges with unit counts and amounts. This makes the API suitable for combining ownership research with assessed value and transaction analysis in a single request.
- Look up current property owners and mailing addresses by parcel ID for title research
- Pull multi-year valuations to track assessment changes on residential or commercial parcels
- Extract building square footage, year built, and condition for automated property condition scoring
- Retrieve sales history including grantor, grantee, and sale price for comparable sales analysis
- Identify tax exemptions applied to a parcel when evaluating effective tax burden
- Aggregate land use, frontage, and depth data across multiple parcels for site selection workflows
- Search by street address to resolve a parcel ID before fetching full assessment records
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 100 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 250 req/min |
One credit = one API call regardless of which marketplace API you call. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does qPublic offer an official developer API?+
What does the `search_properties` endpoint return when multiple results match?+
total_results count. Each object includes parcel_id, account_number, owner, property_address, city, and legal_description. The full detail object is only included when the search resolves to exactly one matching parcel.How many years of valuation data does `get_property_details` return?+
valuations field is an object keyed by year (e.g. 2025, 2024). The number of available years depends on what the individual county assessor has published on qPublic, and varies by jurisdiction. There is no guaranteed minimum number of historical years across all counties.Does the API cover all counties that use qPublic?+
Can I retrieve tax bill amounts or current tax due balances?+
fees records with assessment, units, and amount fields, and exemptions data, but live tax bill balances or payment status are not part of the response. You can fork this API on Parse and revise it to add an endpoint targeting tax bill data if that information is available on the relevant county's qPublic pages.