The Model Match API: Build Internal Tools on Mortgage Data

The Model Match API is a way to feed our mortgage and real estate data — loan officers, real estate agents, companies, loans, and properties — straight into the software your team already uses. Instead of logging into another website to look something up, the data flows directly into your own dashboards, spreadsheets, and internal tools.

If that sounds technical, it isn’t — not for the person deciding whether it’s worth it. This post explains, in plain terms, what the Model Match API does and why it’s valuable.

First, what is an API?

An API is simply a way for two pieces of software to talk to each other. When a weather app shows you the forecast, it’s quietly pulling that from a weather service’s API in the background. You never see it happen — you just get the answer.

The Model Match API works the same way, for mortgage and real estate data. Your tools ask for the data they need — say, the top-producing loan officers in a city — and it comes back in seconds, already organized and ready to use.

The problem it solves: data that’s scattered and messy

Most companies that want mortgage and real estate data end up trying to collect it themselves, from dozens of scattered public sources — county records, licensing databases, and more. It’s tedious, error-prone work:

• The same loan officer shows up three different ways, so records get double-counted or mismatched.
• Information goes out of date, and nobody notices until a decision is made on stale numbers.
• A small change at one source can quietly break the whole pipeline, leaving gaps.

Teams end up spending more time cleaning data than actually using it. That’s the tax the API removes.

The value: one clean, always-current source

With the Model Match API, you get a single, tidy, up-to-date source of mortgage and real estate data, delivered in the same consistent format every time. No cobbling sources together, no maintaining a fragile pipeline, no giant files to wrangle.

That means your team spends its energy on the actual product — the tool, the report, the decision — instead of the plumbing underneath it. And because it’s always current, what you build stays accurate on its own.

What teams build with Model Match data

You don’t have to use Model Match the way we ship it. Once the data flows into your own systems, you can build exactly the tool you wish existed. A few examples:

• A live loan officer scoreboard. See who’s producing in your markets and how much — refreshed whenever you want, instead of a spreadsheet someone rebuilds by hand every quarter.
• A shortlist of agents worth partnering with. Score real estate agents the way your team thinks about a good fit, and surface the best prospects automatically.
• A morning market update in Slack. Closings, new listings, and what shifted overnight — delivered to your team’s channel each day, so nobody has to pull a report.
• A CRM that fills in its own blanks. Turn half-empty contact records — often just a name and a city — into complete ones, backfilled with production and company details.

None of these require a big engineering team. If you can stand up a simple internal dashboard, you can build these.

For your engineers

If you do have a developer on the team, here’s the reassuring part: it’s a standard, modern API. One secure key, simple requests, and results that come back in neat pages so nothing ever gets overwhelmed — even at nationwide scale. This is all it takes to ask for the top-producing loan officers in Texas:

curl -X POST https://api.modelmatch.com/v1/originators \
  -H "x-api-key: $MM_KEY" \
  -d '{ "flatFilters": { "state": "TX" }, "sort": [{ "field": "totalVolume", "order": "desc" }] }'

There’s also a TypeScript SDK for a typed, drop-in experience, bulk delivery for teams loading a data warehouse, and an MCP server if the “internal tool” you have in mind is really an AI assistant. The developer docs cover all of it.

Plug it into the tools you already use

Here’s where the value gets concrete. Because it’s a standard API, Model Match data drops into whatever your team already runs on — no special connector required. Take the loan officers you pulled above (we’ll call each one lo) and push them straight into your CRM or project board. Same handful of lines, three common tools.

HubSpot — add each loan officer as a company (or contact) so they show up right in your pipeline, with production and NMLS ID attached:

// Add a Model Match loan officer to HubSpot as a company
await fetch("https://api.hubapi.com/crm/v3/objects/companies", {
  method: "POST",
  headers: {
    Authorization: "Bearer " + HUBSPOT_TOKEN,
    "Content-Type": "application/json",
  },
  body: JSON.stringify({
    properties: {
      name: lo.name,
      nmls_id: lo.nmlsId,
      annualrevenue: lo.totalVolume,
      city: lo.city,
      state: lo.state,
    },
  }),
});

Salesforce — create a Lead for the same loan officer, mapped to your own fields:

// Create a Salesforce Lead from a Model Match loan officer
await fetch(SF_INSTANCE + "/services/data/v60.0/sobjects/Lead", {
  method: "POST",
  headers: {
    Authorization: "Bearer " + SF_TOKEN,
    "Content-Type": "application/json",
  },
  body: JSON.stringify({
    LastName: lo.name,
    Company: lo.company,
    City: lo.city,
    State: lo.state,
    AnnualRevenue: lo.totalVolume,
  }),
});

Monday.com — drop each prospect onto a board as an item, passing production and market as the column values:

# Monday.com — add a loan officer to a board as an item
mutation AddProspect($cols: JSON!) {
  create_item(
    board_id: 1234567890
    item_name: "Marcus Delgado"
    column_values: $cols
  ) {
    id
  }
}

The pattern never changes: read from Model Match, write to the tool. The same few lines work for Airtable, Notion, a Google Sheet, or your own data warehouse — and real estate agents flow in exactly the same way as loan officers.

How to get started

Ready to build? Tell us what you’re building and we’ll set you up with API access and a quick-start guide — usually the same day.

FAQs

What is the Model Match API? The Model Match API is a way to feed Model Match's mortgage and real estate data — loan officer production, real estate agents, companies, loans, and properties — directly into your own software and internal tools, instead of looking it up on a website. Your tools request the data they need and get it back instantly, in a clean, consistent format.

What kind of data can I get from it? Loan officer production (volume, units, and loan-type mix), real estate agents and their activity, mortgage companies and lenders, loans, property records, and broad market trends for a city, county, or state. In short, the same mortgage and real estate intelligence that powers Model Match, delivered to your tools.

Can I connect it to HubSpot, Salesforce, or Monday.com? Yes. Because it's a standard API, you can pull loan officers, real estate agents, and companies from Model Match and push them into HubSpot, Salesforce, Monday.com, Airtable, or any tool with an API — usually in a few lines of code. It's the same read-from-Model-Match, write-to-your-tool pattern for each.

Do I need to be technical to use it? To connect it, yes — a developer wires it into your systems once. But the value is for everyone: once it's connected, your team gets live dashboards, reports, and tools built on always-current data, without anyone logging into another website or cleaning a spreadsheet.

How do I get access? Request access with a quick note on what you're building, and we'll set you up with an API key and a quick-start guide — usually the same day.