JB PARCELWhat is an API? A plain-English answer
When you look up a property on a website, you click around and read the answers off the screen. An API is the same conversation without the screen. One program asks a question in a fixed format, another program answers in a fixed format, and no human has to click anything. API stands for application programming interface, which is a long way of saying "the counter where programs place orders."
The restaurant picture
A useful picture: a restaurant. You do not walk into the kitchen and cook. You hand a waiter an order written a specific way, and food comes back a specific way. An API is the waiter. The kitchen is the database. The menu is the documentation, which lists exactly what you can ask for and how to phrase it.
Here is what a real API request looks like in plain terms. Your program says: "GET me parcels in Davidson County, Tennessee, where the owner lives out of state." The server answers with a structured list: parcel ID, owner name, mailing address, assessed value, one row per property. The format is called JSON, and it is just labeled text that programs read easily. You can read it too; it looks like a filled-in form.
Why an investor should care
Because clicking through properties one at a time does not scale, and copying results into a spreadsheet by hand invites typos. With an API you ask once and get hundreds of rows back in a form a spreadsheet, a script, or an AI assistant can use directly. Absentee-owner lists, tax-value screens, sale-date filters: each of those is one request instead of an afternoon.
A few real workflows people run against parcel APIs:
- A weekly buy-box pull. The same search you would click through on the map, run on a schedule, with new matches dropped into a spreadsheet.
- Enriching a list you already have. You have 200 addresses from driving for dollars; a script asks the API for the owner and mailing address of each one.
- Feeding a model. Underwriting spreadsheets that read appraised value, lot size, and last sale straight from the source instead of from a retyped copy.
The words you will run into
| Term | What it actually means |
|---|---|
| API key | A password for programs. It tells the server whose account to meter the request against. Keep it private, same as any password. |
| Endpoint | One specific question the API can answer, like /api/search. An API is a set of endpoints. |
| Request and response | The order you place and the answer that comes back. Responses arrive as JSON, which is labeled, structured text. |
| Rate limit | The speed cap, there so one user cannot flood the server. Hitting it is normal; your program just waits and continues. |
| 429 | The server saying "slow down." It is not an error in your setup and not a broken service. |
Do you have to write code?
No. Tools like Claude, spreadsheet plugins, and no-code platforms can call APIs for you; you describe what you want and they place the order. That is exactly what MCP, the newer standard for connecting AI assistants to data, was built for. If that sounds like the right starting point, read What is MCP? next, then the two-minute setup in Use JB PARCEL with AI tools.
And if you do write a little code, a parcel API is one of the friendlier places to start: every request is a plain web address, and every answer is a list of properties you can check against the map with your own eyes on the API page.
Professional accounts include API access with a generous daily allowance. Not open for signup yet: join the waiting list and your first month of Professional is on us at launch.
See the API page