Frequently Asked Questions

Everything you need to know about the Indiana Property Data API.

General

What is the Indiana Property Data API?

A REST API providing access to 3.7 million parcels, 7+ million assessment records, sales transactions, and building details across all 92 Indiana counties. It consolidates data from the Indiana DLGF, county assessors, and multiple CAMA systems into a single, fast, well-documented API.

Who is this API for?

Developers building PropTech products, real estate analytics tools, insurance underwriting systems, mortgage/lending platforms, government applications, and academic research projects. Anyone who needs programmatic access to Indiana property data.

How do I get started?

Sign up for a free account to get your API key. The free tier includes 50 requests per day -- enough to prototype and test. Our quick start guide walks you through your first request in under 5 minutes.

What response format does the API use?

All endpoints return JSON. Parcel geometry is available as GeoJSON (RFC 7946). The API follows RESTful conventions with consistent response envelopes, pagination, and error codes documented in the API reference.

Pricing & Plans

Is there a free tier?

Yes. The free tier includes 50 requests per day, 10 requests per minute rate limit, and 1 API key. No credit card required. It covers all endpoints -- there are no feature restrictions, only volume limits.

What happens if I exceed my daily request limit?

On the free tier, requests beyond 50/day return a 429 status code until the next day. On paid tiers (Starter and Growth), you can enable overage billing -- additional requests are charged at a per-request rate ($0.003/req for Starter, $0.001/req for Growth) so your application continues working without interruption.

Can I switch plans at any time?

Yes. Upgrades take effect immediately and are prorated. Downgrades take effect at the end of your current billing period. You can manage your subscription from the dashboard billing page.

What does Enterprise pricing include?

Enterprise plans include unlimited requests, custom rate limits, dedicated support, SSO integration, SLA guarantees, and IP allowlisting. Contact us for custom pricing based on your needs.

Do you offer annual billing?

Yes. Annual billing is available for Starter and Growth tiers at a discount. Contact us or select the annual option in your billing dashboard.

Data Coverage

How many parcels are in the database?

Approximately 3.7 million parcels covering all 92 Indiana counties. This includes residential, commercial, industrial, agricultural, and exempt properties.

How often is the data updated?

Parcel geometry and Gateway assessment data are updated quarterly from the DLGF. CAMA data from county systems (Beacon, Elevate, self-hosted ArcGIS) is refreshed on a per-county schedule, typically monthly. Sales data from the Indiana SDF is updated annually. Check the status page for per-county freshness timestamps.

Which counties have CAMA data?

39 of 92 counties have enriched CAMA data from county assessment systems (Beacon, Elevate, self-hosted ArcGIS). CAMA data includes additional fields like owner name, review year, legal acreage, and property class codes. All 92 counties have foundational Gateway assessment data from the DLGF.

What is the difference between Gateway and CAMA data?

Gateway data comes from the DLGF's statewide fixed-width data files and includes assessed values (land, improvement, total), property class, and basic characteristics. CAMA data comes from county-level assessment systems and adds richer detail: owner names, sale dates/prices, legal acreage, grade, condition, and building specifics. When both sources exist for a county, CAMA fields are preferred.

Can I get historical assessment data?

Yes. The /parcels/{id}/assessments endpoint returns assessment records across multiple years and data sources. Each record includes the assessment year, source (Gateway vs CAMA), and full assessed value breakdown.

Does the API include property geometry/GIS data?

Yes. Parcel boundary polygons are available as GeoJSON through the parcels endpoint. The API also supports spatial queries: radius searches (find parcels within X miles of a point) and bounding box queries (find parcels within a geographic rectangle).

Technical

What authentication method does the API use?

API key authentication via the X-API-Key header. Each account can have multiple API keys (1 on free, 3 on Starter, 5 on Growth, 10 on Enterprise). Keys can be rotated with a 24-hour grace period where both old and new keys work.

What are the rate limits?

Rate limits vary by tier: Free (10 req/min), Starter (60 req/min), Growth (300 req/min), Enterprise (custom). Rate limit headers (X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset) are included in every response.

Do you support bulk data downloads?

The Growth and Enterprise tiers support bulk endpoints with higher page sizes (up to 1,000 records per request vs 100 on lower tiers). For full county-level data exports, contact us about Enterprise bulk access.

Do you have client SDKs?

TypeScript and Python SDKs are in development. In the meantime, the API is a standard REST API that works with any HTTP client. The full OpenAPI 3.1 specification is available for code generation.

What is the average response time?

The median response time is approximately 127ms for parcel lookups. Spatial queries and search operations are typically under 500ms. The status page shows real-time latency metrics for each service.

Ready to get started?

Sign up for a free API key and make your first request in under 5 minutes.

Get Your Free API Key