---
title: "Whether a jurisdiction is served, and its notice rules"
method: GET
path: "/v1/jurisdictions/resolve"
---

# Whether a jurisdiction is served, and its notice rules

`GET /v1/jurisdictions/resolve`

## Request

- Base URL: `https://api.evictionsapi.com`
- URL: `https://api.evictionsapi.com/v1/jurisdictions/resolve`
- Auth: one of:
  - HTTP bearer
  - HTTP bearer

## Query parameters

- `state` string, required
- `county` string
- `city` string

## Response `200`

Served status, `handling`, jurisdiction ids and the grounds. With a live key every US state and DC is served with `handling: "attorney_direct"`, `action: null` and, for each ground, `notice: null` and the facts intake requires (`requiredFacts`) and, where `fullService` is true, the facts that place's documents ask for beyond them (`documentFacts`: `notice` and `filing`, by where the case starts, and `conditional`, facts asked for only when another holds (with `past: true`, when that fact is a date before today, such as a lease end date that has passed), `ledgerItemised`, where the place's documents itemise the ledger by kind of charge (`notice`: the notice demands only what is past due on its date; `filing`: the filing states the amounts by kind), and `defaults`, the pack's own default where a fact has one). They apply only to a case created with `service: "full"`: ask an attorney-path case for the intake facts alone; anything else is `served: false`. With a test key (`handling: "automated"`) the fictional test state answers with its notice rules for each ground. `fullService` says whether a case created here with `service: "full"` is handled by us as your agent (no attorney reviews it); where it is false, a managed-service request answers 409 `service_unavailable` with its operational reason. This does not establish a legal requirement for counsel. `county` may be written as the US Census Bureau lists it or by its short name, in any case ("Henry County", "henry"); a county the state does not have answers 400 `invalid_request`. `court` is the court the place's rules say a case goes to, with the county ("Magistrate court of Henry County"), or `null` where no rule pack covers the place. `courts` lists, where `fullService` is true, the courts a full-service case's `managedContext.courtId` may name, each with the `forums` its `managedContext.forum` may name; it is empty otherwise.

- object

## Other responses

- `400`: The request is invalid.
- `401`: The credential is missing or invalid.
- `403`: The credential is not allowed to do this (`forbidden`). For a signed-in session: `permission_denied`, the person's role in the organization lacks the permission this needs (ask an owner); `no_organization`, the person belongs to no organization yet (start one with `POST /v1/me/organizations` or accept an invitation).
- `404`: Not found.
- `409`: The request conflicts with the current state: for a case, it is not in a state that allows this, or its details were erased (`erased`); for an API key, a limit or the key in use.
- `422`: The case did not pass a check.

---

[API](https://skmtc.dev/evictionsapi/apis/evictions-api.md) · [All operations](https://skmtc.dev/evictionsapi/apis/evictions-api/llms.txt) · [OpenAPI document](https://skmtc.dev/evictionsapi/apis/evictions-api/revisions/28459213a1a3?raw)