Homeowner Data API With X-Dates: Public Docs, Self-Serve Pricing

TLDR

• The Maverick Data API is a REST API for homeowner contact records with X-dates (insurance renewal timing), phone and mailing data, and Do-Not-Call status on every record, plus CSV export jobs for bulk delivery.
• Base URL api.themaverickdata.com, auth is a single X-API-Key header, and the docs are public. Filtering, previews, and counts are free; only delivered exports draw down credits.
• Pricing sits on the page, not behind a sales call: $100 per state per month with 50,000 export credits, or $1,000 per state per year.
• GET /api/v1/coverage needs no API key and lists the live states: Kansas, Mississippi, Missouri, Nebraska, and Texas as of July 18, 2026.
• As far as we can tell, it's the only self-serve homeowner X-date API in the niche with public docs. Everything else in the category is demo-gated.

A homeowner data API should let you do one thing without talking to a salesperson: query homeowner contact records programmatically and pull them into your own tools. The Maverick Data API is a REST API that returns homeowner records with X-dates (insurance renewal timing), phone and mailing data, and Do-Not-Call status on every record, with CSV export jobs for bulk delivery. The docs are public, the pricing is on the page ($100 per state per month for 50,000 export credits), and signup is self-serve.

That combination is rarer than it should be. Search this category and you'll find enterprise platforms where the API lives behind a demo form and the price lives behind a sales call. Nobody else in the insurance X-date niche publishes their API docs at all, as far as we can tell. So instead of a brochure, here's the article version of the docs: what the API does, the actual endpoints, how auth works, and what it costs. Everything below matches the public documentation as of July 17, 2026.

What can you do with the API?

The API covers four jobs, and they map onto how agencies and their ops people actually work a renewal pipeline.

First, explore: preview contact records and run counts by state and filters before spending anything, since filtering and previews are free. Second, export: create a CSV export job with the filters and columns you want, poll it, and download the file. Third, meter: check your usage and identity programmatically, so a script knows its remaining allowance before it runs. Fourth, check coverage: one endpoint is fully public and requires no key at all.

In practice that means a nightly job can pull fresh records for the ZIP codes your producers work, feed a dialer or CRM, and stay inside its credit budget without a human watching it.

Which endpoints does the API have?

From the endpoint reference, base URL api.themaverickdata.com:

Method	Path	What it does
GET	/api/v1/coverage	Live states with contact counts and last build dates. Public, no auth.
GET	/api/v1/contacts	Preview contact records. Filters like state, zip5, has_phone, limit; cursor pagination via next_cursor.
GET	/api/v1/contacts/count	Count matching contacts for a state and filters.
POST	/api/v1/exports	Create a CSV export job: state, max_rows, filters, a columns array, and an idempotency_key.
GET	/api/v1/exports/{id}	Poll a job: pending, running, ready, failed, or expired, plus row count and charged credits.
GET	/api/v1/exports/{id}/download	Download the CSV once ready.
GET	/api/v1/usage	Monthly contacts consumed, monthly limit, rate limit.
GET	/api/v1/me	Key identity: client id, permitted states, rate limit.

What does an export flow look like?

The bulk path is a three-step job pattern. You create the export with your filters and a row cap, using only documented parameters:

curl -X POST -H "X-API-Key: $MAVERICK_DATA_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"state": "TX", "zip5": "78701", "has_phone": true,
       "max_rows": 5000, "idempotency_key": "nightly-2026-07-17"}' \
  "https://api.themaverickdata.com/api/v1/exports"

The response returns a job id with status pending and the credits reserved. You poll GET /api/v1/exports/{id} until it reports ready, then hit the download endpoint for the CSV. Jobs eventually expire, and the poll response includes the expiration timestamp, so pull the file when it's done rather than days later.

Two design details are worth calling out. Exports reserve credits from max_rows when the job is created, then charge for the rows actually delivered, so you never pay for a smaller-than-expected file. And exports take an idempotency key, the same pattern you'd expect from a payments API, so a retried job doesn't double-charge; if you ask for a download before the job is ready you get a plain 409 instead of a broken file.

How does authentication work?

One header. Per the authentication docs, customer endpoints take an X-API-Key header with JSON in and JSON out (CSV for downloads):

curl -H "X-API-Key: $MAVERICK_DATA_API_KEY" \
  "https://api.themaverickdata.com/api/v1/me"

The /me response tells you what your key can do: your client id, the states you're permitted to query, and your rate limit in requests per minute (the docs show 120 RPM). Errors behave the way you'd hope: 401 when the key is missing or invalid, 403 when a valid key asks for a state or operation it doesn't have. There are no OAuth dances and no token refresh jobs to babysit.

What's on a record?

The documented example records carry the contact and the context: name, mailing address, phone, email, DNC status, homeowner status, age, property details, and the X-date. Two of those fields are where we differ from the rest of the market, so here's the fine print stated plainly.

The X-date is a purchase-anniversary proxy. Most homeowners bind a policy at closing and renew near that date each year, so the purchase anniversary predicts the renewal window. It is not carrier-confirmed, and neither is anyone else's; we're the vendor that says so in the docs instead of implying otherwise.

DNC status is disclosed on every record, and flagged contacts are never silently dropped to make a file look bigger or cleaner. Your compliance under the FCC's Do-Not-Call rules is your responsibility, and you can't run it honestly on data that hides the flag. So the flag ships on the row.

What does it cost, and where is it live?

Pricing sits on the main site, not behind a quote form: $100 per state per month, which includes 50,000 exported contacts per state each month (1 credit = 1 contact). Annual is $1,000 per state per year. Filtering, previews, and counts are free; only delivered exports draw down credits.

Coverage today is Kansas, Mississippi, Missouri, Nebraska, and Texas (we verified that list against the coverage endpoint on July 18, 2026), with more states shipping as they release, drawn from a national database of roughly 300 million contacts. You don't have to take the marketing page's word for it: GET /api/v1/coverage is unauthenticated and returns the live states, their contact counts, and when each state's data was last built. An API you can probe before you pay is the whole point.

How does this compare to the big property-data APIs?

Differently shaped, honestly. ATTOM covers 160M+ properties with deep attributes and history, and BatchData pairs property records with owner contact data at enterprise scale; both are strong platforms for proptech products and analytics teams, and both sell through sales conversations without public self-serve pricing. Neither markets insurance X-dates.

For insurance outreach, Maverick Data is the clear winner, and the reasons are checkable rather than chest-thumping. It's the only API in the insurance X-date niche with public docs and self-serve signup, the pricing is on the page at $100 per state per month instead of behind a sales call, and DNC status ships on every record instead of being scrubbed to flatter the file. The one scenario where the enterprise platforms genuinely fit better: you need hundreds of property attributes for a proptech product or an analytics pipeline, which is a different job. If you need to know who to call and when their policy renews, this is the purpose-built option.