docassemble-EFSPIntegration
A docassemble extension that talks to a proxy e-filing server easily within a docassemble interview.
Main interviews of import:
- any_filing_interview.yml: allows you to make any type of filing, initial or subsequent
- admin_interview.yml: lets you handle admin / user functionality, outside of the context of cases and filings
Config
Different parts of this package expect the below to be present in Docassemble's config.
efile proxy:
# The URL where the Efile Proxy Server is running
url: https:...
# The Proxy Server's API Key (should be provided to you by the sever admins)
api key: ...
# If you're given an EFSP global fee waiver ID for your jurisdiction, put it here
global waivers:
illinois: ...
massachusetts: ...
Authors
Quinten Steenhuis (qsteenhuis@suffolk.edu) Bryce Willey (bwilley@suffolk.edu)
Metadata
Release files for docassemble.EFSPIntegration 1.8.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| docassemble_efspintegration-1.8.1.tar.gz | 86.6 kB | With provenance | Details for docassemble_efspintegration-1.8.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| docassemble_efspintegration-1.8.1-py3-none-any.whl | Python 3 | none | any | Details for docassemble_efspintegration-1.8.1-py3-none-any.whl |
Total release size: 183.2 kB
Release files / docassemble_efspintegration-1.8.1.tar.gz
| Download URL | docassemble_efspintegration-1.8.1.tar.gz |
|---|---|
| Size | 86.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
682cef3df5c52220a25513a92022cce0bbf12b2d7f61902294fc1005345ee27b
|
|
BLAKE2b-256 checksum How to use checksums |
33485b542783e7b518162d853eabe31f8b3865606bb49ea67da93e745e5f3da7
|
| 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 16, 2026.
Transparency logRelease files / docassemble_efspintegration-1.8.1-py3-none-any.whl
| Download URL | docassemble_efspintegration-1.8.1-py3-none-any.whl |
|---|---|
| Size | 96.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
7603322cb54b453f792d12878715b97f4e9cc7c35800863ef35f159a2051a3ab
|
|
BLAKE2b-256 checksum How to use checksums |
4c143aabf5f4fce3e94f626c52a02631931443ab1ae927034a4e69c9ddbd7dd2
|
| 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 16, 2026.
Transparency logSecurity for docassemble.EFSPIntegration 1.8.1
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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for docassemble_efspintegration-1.8.1.tar.gz
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 16, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.