docassemble.MACourts
A utility package that includes JSON files representing all of the courts in Massachusetts.
Courts automatically scraped from Mass.gov and geocoded with Google Maps.
If the court has a PO box, the PO box will be available in court.address.orig_address
Tests
Mypy:
mypy .
Unittests:
python3 -m unittest discover docassemble
How to update lower_court_code
When e-filing into appeals cases, Tyler expects a very specific code for the lower court that the case is being appealed from. We got a confirmation from Tyler that these values aren't publicly available, so for now they are stored in the tyler_lower_court_code and tyler_prod_lower_court_code attributes
for each object.
These values may occasionally change. And again, as we've gotten little information from Tyler about these values, we don't know when these values change. The only indication is if you start receiving 168, Lower court code not found errors when filing.
To update these values:
- visit and login to https://massachusetts-stage.tylertech.cloud/ofsweb/ (or the production site, https://massachusetts.tylertech.cloud/ofsweb/)
- Once logged in, under "New Filing", click "Start a new case" (or visit https://massachusetts-stage.tylertech.cloud/OfsWeb/FileAndServeModule/Envelope/AddOrEdit).
- Pull up your browser's network tools, refresh the page, and set the location field to be "Appeals Court (Single Justice)".
- In your browser's network tools, look for the request to
GetEnvelopeCodeConfigs. The full URL queried is https://massachusetts-stage.tylertech.cloud/OfsWeb/FileAndServeModule/Envelope/GetEnvelopeCodeConfigs?isLocationChanged=true&locationId=120.
The values we need will be in the JSON returned from that endpoint, under obj["DropDownsLocation"]["LowerCourtCodes"].
Note: I wasn't able to give Lower Court codes to the "Metro South Housing Courts". Tyler's list only includes:
- Housing Court Central
- Housing Court Eastern
- Housing Court, Northeast
- Housing Court, Southeast
- Housing Court, Western
3 maintainers
Metadata
3 maintainers
Release files for docassemble.MACourts 1.5.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| docassemble_macourts-1.5.0.tar.gz | 3.9 MB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| docassemble_macourts-1.5.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 7.8 MB
Release files / docassemble_macourts-1.5.0.tar.gz
| Download URL | docassemble_macourts-1.5.0.tar.gz |
|---|---|
| Size | 3.9 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
17e71dea68361bebd06ae5a03351b92f9a3c0a4503d04affde82b921c990af52
|
|
BLAKE2b-256 checksum How to use checksums |
6e7549b94b37157c6f784d6c886c17a6f71872f061421a45ded2d80089c7a0d4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 11, 2026.
Transparency logRelease files / docassemble_macourts-1.5.0-py3-none-any.whl
| Download URL | docassemble_macourts-1.5.0-py3-none-any.whl |
|---|---|
| Size | 4.0 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c155e93f1fd5a135c39693e4e96e4d67e988624643a9abe22323e62e0bc6fb8c
|
|
BLAKE2b-256 checksum How to use checksums |
3456242e08dfb79c5ceb228da063846cae83e105f5cee01880568f0e1bc31a61
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 11, 2026.
Transparency log
