> ## Documentation Index
> Fetch the complete documentation index at: https://docs.centsless.org/llms.txt
> Use this file to discover all available pages before exploring further.

# GET /jurisdictions — List all jurisdiction rules

> Returns all jurisdiction rules in the Centsless database including enacted, pending, and proposed legislation across all 50 states and territories.

This endpoint returns the full set of jurisdiction rules in the Centsless database, including enacted, pending, and proposed legislation. Use it to build state-selection UIs that reflect current rounding law, audit your coverage before expanding to a new region, or sync jurisdiction data into your own system.

## Endpoint

```
GET https://api.centsless.org/api/v1/jurisdictions
```

## Authentication

All requests require an `x-api-key` header.

## Code example

```bash theme={null}
curl https://api.centsless.org/api/v1/jurisdictions \
  -H "x-api-key: YOUR_API_KEY"
```

## Example response

```json theme={null}
[
  {
    "lookup_key": "AZ",
    "jurisdiction_id": "US-AZ",
    "jurisdiction_level": "state",
    "rounding_mode": "swedish_rounding",
    "enforcement": "mandatory",
    "status": "enacted",
    "legislation": "AZ HB 2938",
    "effective_date": "2025-01-01",
    "notes": "Swedish rounding required statewide.",
    "source_url": "https://leginfo.example.gov/az/hb2938"
  },
  {
    "lookup_key": "IN",
    "jurisdiction_id": "US-IN",
    "jurisdiction_level": "state",
    "rounding_mode": "symmetrical_rounding",
    "enforcement": "permissive",
    "status": "enacted",
    "legislation": "IN SB 243",
    "effective_date": "2025-07-01",
    "notes": "Three-tier operator choice; permissive for retail.",
    "source_url": "https://leginfo.example.gov/in/sb243"
  }
]
```

## Response fields

Each object in the returned array represents one jurisdiction rule.

<ResponseField name="lookup_key" type="string">
  The key used to resolve this rule. Matches the state code, or a hyphen-delimited `state-county` or `state-county-city` string. Example: `AZ`
</ResponseField>

<ResponseField name="jurisdiction_id" type="string">
  Jurisdiction identifier. Example: `US-AZ`
</ResponseField>

<ResponseField name="jurisdiction_level" type="string">
  Where in the hierarchy this rule applies. One of: `federal`, `state`, `county`, `city`
</ResponseField>

<ResponseField name="rounding_mode" type="string">
  The rounding algorithm that applies. One of: `swedish_rounding`, `mandatory_round_down`, `mandatory_round_up`, `symmetrical_rounding`, `nearest_nickel`, `nearest_cent`, `nearest_dime`, `none`
</ResponseField>

<ResponseField name="enforcement" type="string">
  How strictly the rule applies. One of: `mandatory`, `permissive`, `voluntary`, `none`
</ResponseField>

<ResponseField name="status" type="string">
  Legislative status of the rule. One of: `enacted`, `pending`, `proposed`, `failed`, `no_legislation`
</ResponseField>

<ResponseField name="legislation" type="string">
  The bill or regulation that defines this rule. Example: `AZ HB 2938`
</ResponseField>

<ResponseField name="effective_date" type="string">
  The date the rule took effect, in ISO 8601 date format.
</ResponseField>

<ResponseField name="notes" type="string">
  Additional context about the rule's scope or application.
</ResponseField>

<ResponseField name="source_url" type="string">
  URL to the authoritative legislative source.
</ResponseField>