Maryland Eviction Cases - Docket Events & Removals avatar

Maryland Eviction Cases - Docket Events & Removals

Pricing

from $0.03 / 1,000 maryland eviction docket events

Go to Apify Store
Maryland Eviction Cases - Docket Events & Removals

Maryland Eviction Cases - Docket Events & Removals

Maryland's residential eviction docket (public open data, 794,432 events across 462,359 cases, 2022-today): event date and type, case number and case type, county, tenant city/state/ZIP, and the eviction date on the rows where a tenant was removed. Filter by county, case type or event type.

Pricing

from $0.03 / 1,000 maryland eviction docket events

Rating

0.0

(0)

Developer

Wenhao Yang

Wenhao Yang

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

3 days ago

Last modified

Categories

Share

Maryland's residential eviction docket, straight from the Maryland Judiciary. 794,432 docket events across 462,359 cases, from January 2022 through the last closed month.

Low cost

From $0.00005 per record, down to $0.00003 at Gold. Pay only for the records you actually receive - the whole register stays queryable, you are never billed for the scan behind it.

What you get

One row per docket event, with the case attached to it:

  • The event - its date and type (a petition filed, a warrant served, a cancellation, an eviction) and the event comment
  • Who was evicted - the tenant's city, state and ZIP
  • The case - the case number and the case type (failure to pay rent, tenant holding over, wrongful detainer, breach of lease)
  • The court - the county / jurisdiction and the location
  • The removal - the eviction date, on the rows where a tenant was actually removed

A row is an event, not an eviction

The three counts are different, and all three are real:

  • 794,432 rows - docket events (a case contributes several).
  • 462,359 distinct case numbers - the cases.
  • 66,958 rows with an eviction date - the tenant was actually removed.

Set evictedFrom to narrow to the third - it keeps only the removal rows and drops the rest.

Filter it

  • County - county="Baltimore City", county="Montgomery". 24 jurisdictions in total.
  • Case type - Failure to Pay Rent (764,542 events, plus 11 more in a spelling variant the filter also matches), Tenant Holding Over, Wrongful Detainer, Breach of Lease. Matched case-insensitively.
  • Event type - an exact-set match (
    eventType="Petition - For Warrant of Restitution Filed"
    ; the accepted values are listed in the input schema). To find the removals, use evictedFrom (above) rather than eventType, which needs the full value
    Warrant of Restitution - Return of Service - Evicted
    to hit them.
  • Case number - caseNumber is a substring match, so a stored number such as caseNumber="D-01-LT-26-106033-016" returns that one case's events; a shorter prefix (e.g. the base D-01-LT-26-106033) spans every docket number beneath it.
  • Tenant city and ZIP.
  • Date range on the event date, and on the eviction date.

Example inputs

The removals - cases where a tenant was actually evicted since January.

{ "evictedFrom": "2026-01-01", "maxResults": 50 }

One county's docket - combine county and case type.

{ "county": "Baltimore City", "caseType": "Failure to Pay Rent", "maxResults": 50 }

Every event on one case - the case number is the case key.

{ "caseNumber": "D-01-LT-26-106033-016" }

Where the filings are - mode=aggregate returns one count row per county; every group comes back.

{ "mode": "aggregate", "groupBy": "county" }

Or roll it up

Set mode=aggregate and get a rolled-up count by county, event type, case type, year, eviction year or city. Every group comes back - not cut off by maxResults.

Then follow the cases

  • Eviction filings and removals by county, month over month.
  • Every docket event on one case, in order.
  • Failure-to-pay-rent vs. tenant-holding-over, side by side.
  • Which ZIPs see the most removals.

Example output

One removal - county=Baltimore City, evictedFrom=2026-01-01:

{
"platform": "md-evictions",
"source": "maryland-eviction-docket",
"mode": "rows",
"groupKey": "",
"groupCount": "",
"groupBy": "",
"eventDate": "2026-08-27T00:00:00.000",
"eventType": "Warrant of Restitution - Return of Service - Evicted",
"eventComment": "",
"county": "Baltimore City",
"location": "Civil",
"tenantCity": "BALTIMORE",
"tenantState": "MD",
"tenantZip": "21206",
"caseType": "Failure to Pay Rent",
"caseNumber": "D-01-LT-26-106033-016",
"evictedDate": "2026-08-25T00:00:00.000",
"eventYear": "2026",
"evictionYear": "2026",
"sourceUpdatedAt": "2026-09-29"
}

mode=aggregate, groupBy=county - one count row per jurisdiction:

Baltimore 279,094
Baltimore City 152,234
Prince George's 139,738
Montgomery 60,757
Anne Arundel 52,639
Howard 24,532

Notes on the data, from the source

  • Event, case, and eviction are three different things. See above.
  • evictionYear is empty on most rows. It is set only on the events that led to a removal (66,958 of 794,432); use year (the event year) as the general time dimension.
  • Two ways to find a removal, 24 rows apart. evictedFrom matches the 66,958 rows with an eviction date; eventType set to the full value Warrant of Restitution - Return of Service - Evicted matches 66,982 - a few eviction-event rows carry no date. evictedFrom is the safer key.
  • A few case types and event types have source spelling variants (e.g. Breach Of Lease as well as Breach of Lease). The filters match case-insensitively so a query catches both.
  • The register is refreshed monthly; sourceUpdatedAt carries the dataset's own refresh date.
  • Tenant city names are as the court recorded them and are not normalized (BALTIMORE and Baltimore both appear), so a substring match is the right way to search.