MapWise Parcels API

Download OpenAPI spec (JSON) YAML

Quick Start

Base URL

https://maps.mapwise.com/api_v2

Get started in 3 steps

Try the test endpoint — no API key needed. Make a request to /parcels/test to see the response format.
Get your API key — log in to your MapWise account, go to My Account → Parcels API, and generate an API key.
Query the full endpoint — use your API key with /parcels to access all 67 Florida counties.

Authentication

Send your API key on every request to https://maps.mapwise.com/api_v2, one of two ways:

X-API-Key: YOUR_API_KEY
Authorization: Bearer YOUR_API_KEY

To obtain a key, log in to your MapWise account, go to My Account → Parcels API, and generate one. You need a valid subscription and Super Admin privileges.

Data & Pricing

County coverage: all 67 Florida counties with complete sales history and property records.
Data updates: weekly to biweekly from official county property appraiser sources (statewide median under a week).
Per-record billing: $0.06 per record returned (billed monthly).
Test endpoint: free — requests to /parcels/test do not count toward billing.

Monthly Spend Caps

Every account includes a monthly spend cap — $100/month by default. Adjust it from My Account → Parcels API → Monthly Spend Cap (requires the Super Admin or Billing role), up to the account maximum of $1,000/month; for higher limits, contact us about enterprise pricing. Once the cap is reached, further billable requests are declined with 429 until usage resets on the 1st of the month (00:00 UTC). Email warnings send at 50%, 80%, and 100% of the cap.

Security note: a leaked key cannot raise its own cap — spend-cap changes require an authenticated dashboard session, not the API key.

Every billable response includes your current spend state in headers:

X-Billing-Period-Spend-Cents: 1200
X-Billing-Period-Cap-Cents: 3000
X-Billing-Period-Reset: 2026-08-01T00:00:00Z

A cap-exceeded response is distinguishable from rate limiting by its body — error is spend_cap_exceeded — and it carries a Retry-After header set to the period reset.

Rate Limiting & Security

API keys are subject to rate limiting:

Global limit: 60 requests per minute
User limit: 180 requests per minute (burst)

Security best practices:

Store API keys in environment variables — never commit them to version control.
Rotate API keys regularly and use HTTPS for all requests.
Monitor your API usage and rate limits.

Parcels

The interactive reference is temporarily unavailable. View the raw specification: OpenAPI (JSON) · YAML.

Test endpoint data scope

The keyless /parcels/test endpoint accepts every parameter, but results are limited to a fixed scope:

County: ALACHUA only — other counties return empty results.
City: GAINESVILLE only for site-address searches.
Sale dates: 1990-01-01 to 2000-12-31 only.

Use the full /parcels endpoint with your API key for complete access.

Error Responses

All error responses include success: false and an errormsg field.

Status	Description	Common cause
`400`	Bad Request	Missing `searchCounty`, `lat_lon`, or `bbox`
`401`	Unauthorized	Missing or invalid API key
`404`	Not Found	No parcels match the search criteria
`429`	Too Many Requests	Rate limit (60 req/min) or monthly spend cap reached — check the body's `error` field: `spend_cap_exceeded` means wait for the period reset, anything else means back off and retry
`500`	Internal Server Error	Unexpected server failure

Best Practices

Validate all user-supplied input before sending requests.
Check meta.record_count to determine if any results were returned.
Handle non-200 HTTP status codes gracefully in your application.
Implement exponential backoff when you receive a 429 response.
All error responses include success: false and an errormsg field.

Contact & Support

Questions about the API, higher rate limits, or enterprise pricing? Contact us.