Parcel Identifiers (APN, FIPS, Coordinates)
View all Redfin Property Data endpoints →The county parcel record keys for a property: APN (assessor's parcel number), FIPS code, parcelLid and precise latLong coordinates, resolved from a propertyId. Beyond GIS and assessor joins, this is the required first step before calling the climate-risk endpoint — every climate input (lat, lng, fipsCode, apn, parcelLid) comes from this response.
API Features
Live API Demo
🔒 Sign in to try it live
Log in to call this API with your own API key. New accounts get 100 free credits — no card required.
Log in / Sign upNo active API key found. Create one in your Dashboard, then reload this page. Dashboard →
/api/project/redfin/parcel-info API Response (JSON)
{} curl -X GET 'https://api.opendata-api.com/api/project/redfin/parcel-info?key=<API_KEY>&propertyId=40775351'
Query Result
Use Cases
- Extract APN, FIPS and coordinates required to call the climate-risk endpoint.
- Join listing data to county assessor and GIS datasets using parcel identifiers.
- Validate parcel-level location data before running hazard or tax analyses.
- Geocode a portfolio of listings for map-based investment dashboards.
Frequently asked questions
What are APN and FIPS?
APN is the parcel number assigned by the county assessor, FIPS the standard county code; both are common keys for joining listing data onto public-record, tax and GIS datasets.
How precise are the coordinates?
Parcel-level latitude/longitude is returned, ready for map anchoring and hazard queries.
Is a listingId needed as well?
No — this endpoint keys on propertyId alone.