Skip to main content

ecourts Coverage Status PyPI - Latest Version GitHub Tag GitHub Actions Workflow Status docs docs DOI

This is a information retrieval toolkit to fetch case information from the ECourts Service. This is primarily meant for journalists, and law researchers who need bulk access to the ECourts website to get orders, judgements, or lists of cases that match their criteria.

The final goal is to cover all services under the ecourts.gov.in domain, but it currently supports a few services covered at https://hcservices.ecourts.gov.in/ecourtindiaHC/.

It covers all the High Courts and their various benches.

Type of Query Supported Inputs
Search for cases by Case Number 🚧WIP Case Type, Case Number, Year
Search for cases by FIR Number 🚧WIP Police Station, FIR Number†, Year†, Case Status (Pending/Disposed/Both)†
Search for cases by Party Name 🔜Planned Petitioner/Respondent Name, Year†, Case Status (Pending/Disposed/Both)†
Search for cases by Advocate Name 🚫No
Search for cases by Filing Number 🚧WIP Filing Number, Year
Search for cases by Act ✅Yes Act Type, Status
Search for cases by Case Type 🚧WIP Case Type, Year†, Pending/Disposed
Search for Case Orders/Judgement by Case Number 🚧WIP Case Type, Case Number, Year
Search for Case Orders/Judgement by Filling Number 🚧WIP Filing Number, Year
Search for Case Orders/Judgement by Judge Wise 🚫No
Search for Case Orders/Judgement by Party Name 🔜Planned Petitioner/Respondent Name, Year
Search for Case Orders/Judgement by Order Date ✅Yes Date
Get Cause List ✅Yes Date

† - Optional

Case Types

Each of the individual courts use their own numbering system for various case-types. So the same type of case might have different ID depending on the court. This can even vary between various benches of the same High Court. For example, HCB (Habeas Corpus Petition) is numbered the following different ways across various courts (not exhaustive):

Court ID
Madras High Court - Principal Bench 22
Madras High Court - Madurai Bench 164
High Court of Jammu and Kashmir - Jammu Wing 17
High Court of Jammu and Kashmir - Srinagar Wing 171

As such, before doing any kind of work that relies on case type (such as fetching case details, or orders by case type) - you must get the relevant case type idenfiers. You can run:

ecourts get-case-type --state-code SC [--court-code CC] to get the case type identifiers for a particular court. If the state-code/court-code identifiers are not provided, the case types will be fetched for all known courts. A list of all known courts is available at courts.csv published as part of the source code.

Act Types

Similar to Case Types, Act idenfiers are different between courts. You can use

ecourts get-act-type --state-code SC [--court-code CC] to get the act type identifiers for a particular court.

Types

The primary two classes that most users will deal with are Court, and ECourt. A court is one of the high court benches covered at https://hcservices.ecourts.gov.in/ecourtindiaHC/, and an ECourt is the primary class that deals with the website.

Other entities involved are more legal in nature:

Documentation

Guiding Principles

  • Make it easy to fetch case information.
  • Store information in accessible formats, for easy retrieval and querying.
  • Use standard identifiers, such as ISO-3166 for state codes.
  • Be nice to the ecourts website. Retry failed requests, but do not hammer the site. In case of 5xx errors, wait for a while before retrying.

Citation DOI

If you use this for any research purposes, please use the following citation information.

DOI: https://doi.org/10.5281/zenodo.13324986

You can check various citation formats on the Zenodo Website or on GitHub by clicking "Cite this repository". Since this is a dynamic software - it depends on the ecourts website, please cite the Zenodo ID 13324986 as it will always point to the latest version of the software.

LICENSE

Licensed under GPL3-or-later. If you run this code, you are responsible for the legal implications of the same. The tool is intentionally single-threaded, and does not offer any parallelism. This is to avoid overloading the ecourts website servers, which are already quite slow. Please note sections 15-16 of the LICENSE, which are summarized here:

There is no warranty for the program, to the extent permitted by
applicable law. In no event unless required by applicable law or agreed to in
writing will any copyright holder, or any other party who modifies and/or
conveys the program as permitted above, be liable to you for damages,
including any general, special, incidental or consequential damages arising
out of the use or inability to use the program.

As part of GPL3 obligations:

You may copy, distribute and modify the software as long as you track changes/dates in source files. Any modifications to this code must also be made available under the GPL along with build & install instructions.

Release files for ecourts 0.0.8

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for ecourts 0.0.8
File Size Uploaded
ecourts-0.0.8.tar.gz 280.1 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for ecourts 0.0.8
File Interpreter ABI Platform
ecourts-0.0.8-py3-none-any.whl Python 3 none any Details

Total release size: 320.2 kB

Release files / ecourts-0.0.8.tar.gz

Download URL ecourts-0.0.8.tar.gz
Size 280.1 kB
Tags Source
SHA-256 checksum
How to use checksums
29909021c87364f886330c0a7117468a2351dd260dd62fd74f7ad852520f6033
BLAKE2b-256 checksum
How to use checksums
c2acffa2fd1f9b964a7c465070a385d80ffe8305b375928c7017156040043694
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.0.1 CPython/3.12.8

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 Dec 17, 2024.

Transparency log

Release files / ecourts-0.0.8-py3-none-any.whl

Download URL ecourts-0.0.8-py3-none-any.whl
Size 40.1 kB
Tags Python 3
SHA-256 checksum
How to use checksums
42eed363476e430ba59f1e052f305046e7a43aed68e976c9b9ead101a56b7453
BLAKE2b-256 checksum
How to use checksums
9f4e2d43d20c2fd1c0bf222268255bcbe0e28e65ae0b24c4faffd9c9ea5fcea0
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.0.1 CPython/3.12.8

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 Dec 17, 2024.

Transparency log

Release history Release notifications | RSS feed

This release

0.0.8 This release

2 release files

0.0.7

2 release files

0.0.6

2 release files

0.0.5

2 release files

0.0.4

2 release files

0.0.3

2 release files

0.0.2

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page