Jefferson Parish Assessor Scraper

Search the official Jefferson Parish assessor website and export useful parcel assessment records as structured JSON.

The Actor supports owner, physical-address, parcel-number, and subdivision/block/lot searches. It follows each official result to collect parcel identity, owners, addresses, legal description, property classes, assessed and market values, deeds, locations, and source links.

It is designed for repeatable property due diligence and assessment comparison. It does not claim to provide billed taxes or historical snapshots that are not displayed by the source.

What can you do with the Jefferson Parish assessor scraper?

• Look up parcels owned by a person or organization.
• Resolve a physical address to official assessment records.
• Retrieve one known parcel by parcel number.
• Search a subdivision and narrow it by block and lot.
• Export current assessed and market values to a spreadsheet.
• Capture source URLs for review and audit trails.
• Schedule recurring runs and compare datasets in your own workflow.
• Feed normalized parcel records into underwriting or due-diligence systems.

Who is this Actor for?

Property researchers can turn public parcel searches into consistent datasets.

Real-estate investors can collect owner, location, legal-description, and valuation context before deeper diligence.

Tax and assessment professionals can retrieve current source-displayed assessments for review.

Data teams can integrate official Jefferson Parish parcel records into recurring pipelines.

Portfolio managers can schedule the same search and compare current records with prior run datasets.

Why use this Actor?

The public website is useful for individual lookups, but repeated manual searches are difficult to automate reliably.

This Actor:

1. establishes the public source session;
2. submits the official search form;
3. follows matching parcel links;
4. normalizes detail tables into typed records;
5. respects your maxItems limit;
6. preserves official detail and map links.

No browser or paid proxy is automatically used. The implementation uses the public server-rendered source pages directly.

Data extracted

Field	Meaning
parcelNumber	Official Jefferson Parish parcel number
assessmentYear	Assessment listing year displayed by the source
primaryOwner	Primary owner shown on the parcel
mailingAddress	Mailing address displayed for the owner
physicalAddress	Physical property address
ward	Parish ward identifier
propertyType	Source property type, such as REAL
legalDescription	Source-displayed legal description
assessedValue	Total assessed value
marketValue	Total market value
propertyValues	Assessment components by property class
deeds	Public deed rows shown on the parcel page
owners	Current and prior owner rows displayed by the source
locations	Subdivision, block, and lot rows
subdivision	First subdivision value for convenient tabular use
block	First block value for convenient tabular use
lot	First lot value for convenient tabular use
mapUrl	Official assessor map link, when shown
sourceUrl	Official parcel detail URL
scrapedAt	Extraction timestamp in ISO 8601 format

A missing source value is returned as null or an empty nested array.

Getting started

1. Open the Actor in Apify Console.
2. Select a value under Search by.
3. Enter the corresponding owner, address, parcel, or subdivision value.
4. Set Maximum parcels to control output volume.
5. Click Start.
6. Open the Dataset tab to inspect or download records.

For a quick test, use:

{
  "searchType": "parcel",
  "parcelNumber": "0100000082",
  "maxItems": 1
}

Input parameters

Input	Type	Description
searchType	string	owner, address, parcel, or subdivision
ownerName	string	Owner text in the source's LAST,FIRST style
address	string	Physical street-address text
parcelNumber	string	Official parcel number
subdivision	string	Subdivision name
block	string	Optional block for subdivision search
lot	string	Optional lot for subdivision search
startUrls	array	Official www.jpassessor.com/Parcel/Details URLs
maxItems	integer	Maximum parcel records, from 1 through 500

Use either startUrls or search fields, not both. block and lot are supported only with subdivision searches.

Search examples

Search by owner:

{
  "searchType": "owner",
  "ownerName": "SMITH",
  "maxItems": 25
}

Search by address:

{
  "searchType": "address",
  "address": "746 12TH ST",
  "maxItems": 5
}

Search by subdivision, block, and lot:

{
  "searchType": "subdivision",
  "subdivision": "SLATTERYVILLE",
  "block": "2",
  "lot": "16",
  "maxItems": 5
}

Extract an official detail URL:

{
  "startUrls": [
    {
      "url": "https://www.jpassessor.com/Parcel/Details?ParcelID=0100000082"
    }
  ],
  "maxItems": 1
}

Output example

The default dataset contains one object per accepted parcel. A current run can produce:

{
  "parcelNumber": "0100000082",
  "assessmentYear": 2026,
  "primaryOwner": "SMITH,BRENDA LEE",
  "mailingAddress": "746-48 12TH ST GRETNA LA 70053 USA",
  "physicalAddress": "746 12TH ST",
  "ward": "10",
  "propertyType": "REAL",
  "legalDescription": "LOT 16 SQ 2 SLATTERY #1",
  "assessedValue": 5370,
  "marketValue": 53700,
  "subdivision": "SLATTERYVILLE",
  "block": "2",
  "lot": "16",
  "sourceUrl": "https://www.jpassessor.com/Parcel/Details?ParcelID=0100000082",
  "scrapedAt": "2026-08-18T06:08:00.000Z"
}

Nested propertyValues, deeds, owners, and locations are also included. The example reflects source-observed structure; public records can change.

How much does it cost to extract Jefferson Parish parcel assessments?

Pricing uses one start event per run plus one tiered item event per saved parcel. At the BRONZE tier, the run start is $0.005 and each saved parcel is $0.004. Higher-volume tiers automatically reduce the per-parcel price.

Saved parcels	BRONZE price calculation
1	$0.005 start + 1 × $0.004 item
10	$0.005 start + 10 × $0.004 item
25	$0.005 start + 25 × $0.004 item
100	$0.005 start + 100 × $0.004 item

Only useful records written to the default dataset receive an item charge. No-result searches have no item charge, but the one-time start event still applies. Platform limits and your account tier can affect the final displayed total.

Scheduling assessment comparisons

Apify schedules can run the same saved input daily, weekly, or monthly. Each run produces a timestamped dataset.

A typical comparison workflow is:

1. save a stable owner, parcel, or subdivision input;
2. schedule the Actor;
3. export each completed dataset;
4. join records by parcelNumber;
5. compare primaryOwner, assessedValue, marketValue, or nested owner rows;
6. alert only on changes relevant to your process.

The Actor returns current source data. It does not create an authoritative historical record inside the source. Your workflow is responsible for retaining and comparing prior datasets.

Export and integrations

The dataset can be downloaded as JSON, CSV, Excel, XML, or RSS from Apify Console.

Common integrations include:

• Google Sheets for review lists;
• Airtable for property research queues;
• webhooks for completed-run notifications;
• Make or Zapier for downstream routing;
• cloud storage for scheduled snapshots;
• Python, JavaScript, SQL, or BI pipelines for comparisons.

Nested arrays are preserved in JSON. For flat CSV workflows, use the top-level parcel, owner, address, location, and value fields first.

Run through the API with cURL

Replace YOUR_TOKEN with an Apify API token:

curl -X POST \
  "https://api.apify.com/v2/acts/automation-lab~jefferson-parish-property-assessment-records/runs?token=YOUR_TOKEN&waitForFinish=120" \
  -H "Content-Type: application/json" \
  -d '{"searchType":"parcel","parcelNumber":"0100000082","maxItems":1}'

Fetch the run's default dataset through the dataset URL returned by the API.

Run through the API with JavaScript

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('automation-lab/jefferson-parish-property-assessment-records').call({
  searchType: 'address',
  address: '746 12TH ST',
  maxItems: 5,
});

const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);

Run through the API with Python

import os
from apify_client import ApifyClient

client = ApifyClient(os.environ['APIFY_TOKEN'])
run = client.actor('automation-lab/jefferson-parish-property-assessment-records').call(
    run_input={
        'searchType': 'subdivision',
        'subdivision': 'SLATTERYVILLE',
        'block': '2',
        'lot': '16',
        'maxItems': 5,
    }
)
items = client.dataset(run['defaultDatasetId']).list_items().items
print(items)

Use with MCP and AI assistants

Add the Apify MCP server to Claude Code:

claude mcp add --transport http apify \
  "https://mcp.apify.com?tools=automation-lab/jefferson-parish-property-assessment-records"

Claude Desktop, Cursor, and VS Code setup

Use this equivalent configuration in Claude Desktop, Cursor, or VS Code:

{
  "mcpServers": {
    "apify": {
      "url": "https://mcp.apify.com?tools=automation-lab/jefferson-parish-property-assessment-records"
    }
  }
}

Example prompts:

• “Look up Jefferson Parish parcel 0100000082 and summarize its assessment.”
• “Export up to 25 parcels for owner SMITH and return parcel number, address, and market value.”
• “Find Slatteryville block 2 lot 16 and include ownership and deed context.”

Review public-record output before relying on an AI-generated conclusion.

Reliability and limits

• The Actor reads the public official website without login.
• It uses a bounded direct-HTTP session and does not enable an automatic paid proxy fallback.
• Source timeouts, maintenance, or markup changes can cause a run to fail rather than return misleading empty data.
• Search matching follows the official site's behavior.
• Broad owner or subdivision searches may have many matches; use maxItems intentionally.
• Maximum output is 500 parcels per run.
• Detail requests use conservative bounded concurrency.
• Values reflect the source at extraction time and may be preliminary or change later.
• Billed tax is outside this Actor's output contract.
• Unobserved historical assessment snapshots are not invented.

Responsible use and legality

The Actor accesses public Jefferson Parish Assessor pages. Public availability does not remove your responsibility to use the data lawfully.

Before processing or redistributing records:

• review the source site's terms and notices;
• comply with applicable privacy, public-record, housing, and anti-discrimination rules;
• collect only the volume needed for a legitimate purpose;
• secure exported ownership and address data;
• verify material decisions against the official source or Assessor's Office.

This Actor is not legal, tax, appraisal, or title advice.

Troubleshooting

Why did my search return no records?

Check the format expected by the official source. Owner searches commonly work best as LAST,FIRST without a space. Try a shorter address or subdivision value and confirm it manually on the public site.

Why did the run fail instead of returning an empty dataset?

The Actor validates the expected search and detail page structure. If the source returns maintenance content, a block, or an unexpected page, failing is safer than presenting it as a true no-result search. Retry later after checking source availability.

Why is a field null?

Not every official parcel page displays every deed, map, location, or owner-history value. Missing source values remain null or empty arrays.

Can I enter multiple searches in one run?

Each run accepts one search workflow or a list of known parcel detail URLs. Use multiple Apify tasks or API calls for unrelated owner/address queries.

Frequently asked questions

Does this include tax bills?

No. The Actor exports source-displayed property assessment values and does not claim billed tax data.

Does this include ownership history?

It includes current and prior owner rows displayed on the current official parcel page. It does not reconstruct records the source does not display.

Can I monitor changes?

Yes. Schedule the same input and compare datasets by parcelNumber in your own storage or automation.

Does it require an Apify proxy?

No. The supported implementation uses direct public HTTP requests.

Can I search personal property?

No. This release is scoped to real-property searches (ParcelType=11).

Related Actors

For multi-market public property research, see other automation-lab Actors:

• Dallas County Property Assessment Scraper
• Cook County Assessor Parcel Scraper
• Clark County Property Records Scraper
• Maricopa County Property Records Scraper

These are separate county sources with separate input and output contracts.

Support

If a run fails, include the run URL, sanitized input, expected search behavior, and whether the official source worked manually. Do not post Apify tokens or private downstream credentials.