CasePrimus.aiby Attestr
Documentation menu
APIv1Updated 14 November 2026

Acts and Sections API

API To Look Up Indian Acts And Sections, And How Serious Each Provision Is

The Acts and Sections API returns what an Indian statutory provision says, how serious it is, and where that grading came from, for central law and state law alike. Nothing about your account is involved: every answer is read from a fixed catalogue, so the same question always returns the same answer.

Search provisions in your own words, browse from jurisdiction to act to section, or send the acts field of a court record exactly as the court wrote it and get back what it means. It is the same reading that sets the risk level CasePrimus.ai gives a case.

Built on certified infrastructure

CasePrimus.ai is operated by Pegadroid IQ Solutions Private Limited, the legal entity behind Attestr's products, which holds ISO/IEC 27001:2022 certification. Data is hosted in India (AWS Mumbai, ap-south-1) and every connection is encrypted in transit. See Trust & Compliance.

Key capabilities

Search in plain words

Search provisions by free text over the act name, the section heading and the description, or by section number.

Browse the catalogue

List the jurisdictions, then the acts in one, then the provisions of an act. Central law comes first, then the states.

Read a court record's act text

Send the acts field of a court record as the court wrote it, for example U/s 138 of N.I Act | Section 223BNSS, and get each provision resolved.

Severity from the provision itself

A provision's severity is read from its own punishment clause, with the punishment, maximum years and whether it is cognizable or bailable.

Central and state law

The catalogue covers central legislation and the legislation of the states.

The same answer every time

Answers come from a fixed catalogue, not from a model, so the same question returns the same answer.

A source you can check

Each provision carries its official title and officialSource, where its text can be checked.

Ungraded provisions on request

Provisions that state no punishment, such as definitions and procedure, are left out by default. Set includeUngraded to see them.

How it works

  1. 1

    Search or browse

    Search with GET /acts/sections, or walk GET /acts/jurisdictions, then GET /acts, then GET /acts/sections?act=....

  2. 2

    Or resolve a court record

    Send the acts field of a court record to POST /acts/sections/resolve, up to 50 lines per call.

  3. 3

    Read what it means

    Each provision comes back with its severity, its punishment, its exposure and where the grading came from.

API definition

Send your API key in the X-CasePrimus-Api-Key header. See Authentication, and Rate limits & errors.

List the jurisdictions the catalogue covers

Lists every jurisdiction with legislation in the catalogue, Central first and the states after it, with how many acts and provisions each holds. This is the first step of browsing. Take a jurisdiction from here to GET /acts, then an act's name from there to GET /acts/sections?act=....

Request URL

GEThttps://api.caseprimus.ai/api/caseprimus/v1/acts/jurisdictions

Request headers

TypeNameValue / descriptionOptional
StringX-CasePrimus-Api-KeyYour API key: {apiKey}Required

No API key yet? See Authentication.

Sample request

Request
BASE="https://api.caseprimus.ai/api/caseprimus/v1"

curl "$BASE/acts/jurisdictions" \
  -H "X-CasePrimus-Api-Key: $CASEPRIMUS_API_KEY"

Responses

200The jurisdictions, Central first.
403Caller lacks case.read, or the plan does not include this product (61470).

Response fields (HTTP 200)

FieldDescription
jurisdictions
array of object
jurisdiction
string

CENTRAL

acts
integer
provisions
integer
Response 200
{
  "jurisdictions": [
    {
      "jurisdiction": "CENTRAL",
      "acts": 836,
      "provisions": 35515
    },
    {
      "jurisdiction": "Andhra Pradesh",
      "acts": 250,
      "provisions": 6479
    },
    {
      "jurisdiction": "Karnataka",
      "acts": 345,
      "provisions": 13650
    }
  ]
}

List acts

Lists the acts in the catalogue, narrowed by jurisdiction or by name, sorted by name. sections is how many provisions the act has, and graded is how many of those carry a severity read from their own punishment clause, which is usually far fewer. Neither filters the list: an act whose provisions state no punishment is still an act. Take an act from here to GET /acts/sections?act=<actName> to read its provisions.

Request URL

GEThttps://api.caseprimus.ai/api/caseprimus/v1/acts

Request headers

TypeNameValue / descriptionOptional
StringX-CasePrimus-Api-KeyYour API key: {apiKey}Required

No API key yet? See Authentication.

Path and query parameters

NameInRequiredDescription
jurisdictionqueryOptionalCENTRAL, or a state's name. Omit for every jurisdiction at once.
qqueryOptionalNarrows by act name. Use this when you half-remember the name - "municipal corporations" finds every state's version of it.
$limitqueryOptionalHow many acts to return. limit is accepted as an alias.
$skipqueryOptionalHow many to skip. skip is accepted as an alias.
limitqueryOptionalAn alias for $limit. Documented because it works; $limit is the form every other paged endpoint in this API uses.
skipqueryOptionalAn alias for $skip.

Sample request

Request
BASE="https://api.caseprimus.ai/api/caseprimus/v1"

curl "$BASE/acts" \
  -H "X-CasePrimus-Api-Key: $CASEPRIMUS_API_KEY"

Responses

200The matching acts, by name.
400A query parameter is malformed (60000).
403Caller lacks case.read, or the plan does not include this product (61470).

Response fields (HTTP 200)

FieldDescription
total
integer
skip
integer
limit
integer
acts
array of object
actKey
string

A stable id for the act within its jurisdiction. Pass `actName` to GET /acts/sections

actName
string
jurisdiction
string
sections
integer

Provisions the catalogue holds for this act.

graded
integer

Of those

Response 200
{
  "total": 345,
  "skip": 0,
  "limit": 3,
  "acts": [
    {
      "actKey": "karnataka|adichunchanagiriuniversityact2012",
      "actName": "ADICHUNCHANAGIRI UNIVERSITY ACT, 2012",
      "jurisdiction": "Karnataka",
      "sections": 60,
      "graded": 1
    },
    {
      "actKey": "karnataka|amityuniversityact2018",
      "actName": "AMITY UNIVERSITY ACT, 2018",
      "jurisdiction": "Karnataka",
      "sections": 61,
      "graded": 1
    }
  ]
}

Search provisions

Searches the catalogue's provisions, most serious first by default. Only graded provisions are returned unless includeUngraded is set. The ungraded ones are those that state no punishment, such as definitions and procedure, and returning them by default would bury the rest. Ask for them when you need to tell "this section carries no penalty" from "this section is unknown to us".

Request URL

GEThttps://api.caseprimus.ai/api/caseprimus/v1/acts/sections

Request headers

TypeNameValue / descriptionOptional
StringX-CasePrimus-Api-KeyYour API key: {apiKey}Required

No API key yet? See Authentication.

Path and query parameters

NameInRequiredDescription
qqueryOptionalFree text over the act name, the section heading and the description.
actqueryOptionalAn act's name, matched EXACTLY once punctuation and a leading "The" are ignored - so the court's spelling usually works, and this returns that act's sections and no other's. It used to match on a prefix, which meant asking for the Code of Criminal Procedure also returned every state amendment act's sections, three different section 1s among them. Use q to search act names partially.
sectionqueryOptionalA section number, e.g. 138 or 7A.
jurisdictionqueryOptional
severityqueryOptional
exposurequeryOptional
basisqueryOptionalHow the provision was obtained.
includeUngradedqueryOptionalInclude provisions with no severity. Off by default.
sortqueryOptional
$skipqueryOptionalHow many to skip. skip is accepted as an alias.
$limitqueryOptionalHow many provisions to return. limit is accepted as an alias.
skipqueryOptionalAn alias for $skip.
limitqueryOptionalAn alias for $limit. Documented because it works; $limit is the form every other paged endpoint in this API uses.

Sample request

Request
BASE="https://api.caseprimus.ai/api/caseprimus/v1"

curl "$BASE/acts/sections" \
  -H "X-CasePrimus-Api-Key: $CASEPRIMUS_API_KEY"

Responses

200A page of provisions.
400The query is not valid (60000).
403Caller lacks case.read, or the plan does not include this product (61470).

Response fields (HTTP 200)

FieldDescription
total
integer

How many match

skip
integer
limit
integer
sections
array of object
key
string

Stable id. Curated provisions keep a short key (NI_138); others are keyed by jurisdiction, act and section.

act
string

The act's short code where the catalogue has one, otherwise INDIA_CODE.

actName
string
section
string
title
string or null
description
string or null

What the section covers, in plain English. Absent where neither the catalogue nor the grading says anything the heading does not already say.

sectionText
string or null

The statute's OWN WORDS for this section, where India Code published the section as text rather than only as a heading - about two provisions in three, overwhelmingly state legislation (India Code serves central law section by section without the body). It is extracted from a published PDF, so the odd word is broken or a line runs on: it is the statute's wording, not a clean transcription of it, and `officialSource` is where to check it.

actContext
string or null

What this PART OF THE ACT covers. Written per act or per chapter, so every section under it carries the same sentence - read it alongside `description`, never instead of it. A provision with no description of its own often still has this, which is why it exists: it is the difference between telling a reader nothing about a section and telling them what kind of law it sits in.

descriptionBasis
enum or null

Where `description` came from. `CURATED` - written and checked by a person. `EXTERNAL_GRADED` - generated from the statute during the grading, and the weaker of the two. Null when there is no description at all; it never describes `actContext`, which is always act-level. Read it before quoting a description as authoritative.

CURATEDEXTERNAL_GRADED
severity
enum or null

Null where the provision states no punishment - a definition, a procedure, a repealed stub.

GRAVESERIOUSMODERATEMINORPROCEDURAL
severityBasis
enum or null

Set only where the severity was read from the section's own maximum punishment rather than written and checked by hand. Such a severity carries less weight in a risk level and can never on its own put a case in the top band. Null means a person wrote it down.

MAX_PUNISHMENT
punishment
string or null

The statute's own words that the severity rests on. The judgement is not checkable; the quote is.

maximumYears
number or null

The ceiling in years, where the clause states one.

death
boolean or null

Whether the provision reaches death or imprisonment for life, which no year count can express. Null where the grading recorded nothing either way, which is most provisions.

exposure
enum or null

What the section puts at stake financially. PROPORTIONATE has no ceiling - it is a multiple of the sum at issue.

PROPORTIONATECRORE_SCALETENS_OF_LAKHSLAKH_SCALEUNDER_1_LAKH
cognizable
boolean or null

Known only for hand-reviewed provisions.

bailable
boolean or null

Known only for hand-reviewed provisions.

commercial
boolean

Whether the provision is commercial rather than personal in character.

jurisdiction
string

CENTRAL, or the state whose legislation it is.

officialTitle
string or null

The heading as India Code prints it.

officialSource
string or null
verifiedAt
string or null

When this entry was last checked against India Code.

riskLevel
integer or null

How much litigation under this provision exposes a party, from 1 (least) to 5 (most), across the whole India Code corpus. Separate from `severity`, which measures the sentence the section carries: a provision can be a modest offence and still be a severe commercial exposure, which is why a dishonoured cheque is graded 5 here and moderate there. Where the two disagree this is the one that decides a case's risk level, except that it never lowers a severity a lawyer reviewed. Null where the provision is outside the graded corpus.

1 to 5

riskScore
integer or null

The same judgement on a finer scale, for sorting. Not a probability and not an amount.

0 to 100

riskBasisTier
enum or null

What the risk level rests on, which is the field to read before relying on one. `knowledge_reviewed` - graded from knowledge of what that act does; `signal` - a real offence or penalty clause was found in the section's own text; `reviewed_no_signal` - the text was read and carries no offence language; `admin` - an administrative or procedural heading; `uncertain` - only a heading was available, no statutory text, so the level is a triage estimate. A level on the `uncertain` tier carries reduced weight in a case's risk level.

true_content_groundedknowledge_reviewedsignalweb_reviewedreviewed_no_signaladminreasoned_uncertainuncertain
litigationCategory
string or null

What kind of dispute the provision gives rise to - for example CORPORATE, INSOLVENCY, TAX_INDIRECT, CRIM_ECON, LABOUR. Describes the provision, not a particular case. One of 25.

litigationCategoryLabel
string or null

The same category in words a person reads - "Economic / white-collar criminal offence" for CRIM_ECON. Published since; before that only the code was, and every screen that had it showed nothing rather than print an enum.

appliesTo
string or null

Who the provision exposes, as a short phrase from the grading's own vocabulary - "Companies", "Individuals, Businesses", "Employers, Employees" and so on, with a handful of older entries still reading `company`, `individual`, `both` or `state`. Not an enum worth relying on: a provision naming individuals can still matter to a company, since directors and officers are frequently named personally.

reviewedByLawyer
boolean

Whether a person wrote and checked this entry. Only these carry a severity that an automated grade is never allowed to lower.

alsoKnownAs
object or null

The same provision in the other code, and WHICH WAY ROUND - so an old citation reads "now BNS 318" and a new one "formerly IPC 420".

basis
enum

Where this provision came from, best attested first. CURATED - written and checked by hand against the statute. STATUTE - read by a model from India Code's own section-level text, with the punishment clause quoted. STATUTE_PDF - read the same way but from an act PDF that had to be split into sections first, for the ten states India Code publishes no sections for; same grading, weaker provenance. HEADING - India Code publishes the heading but the section states no punishment, so there is nothing to grade.

CURATEDSTATUTESTATUTE_PDFHEADING
reviewed
boolean

Whether a lawyer has checked this severity and description. True only for CURATED.

Response 200
{
  "total": 5,
  "skip": 0,
  "limit": 2,
  "sections": [
    {
      "key": "IPC_467",
      "act": "IPC",
      "actName": "Indian Penal Code, 1860",
      "section": "467",
      "title": "Forgery of a valuable security or will",
      "description": "Forging a document that itself creates or transfers value - a cheque, share certificate, deed or will. Punishable with imprisonment for life.",
      "severity": "GRAVE",
      "severityBasis": null,
      "punishment": null,
      "maximumYears": null,
      "exposure": null,
      "death": false,
      "cognizable": true,
      "bailable": false,
      "commercial": true,
      "jurisdiction": "CENTRAL",
      "officialTitle": null,
      "officialSource": null,
      "verifiedAt": null,
      "alsoKnownAs": {
        "key": "BNS_338",
        "act": "BNS",
        "section": "338",
        "title": "Forgery of a valuable security or will",
        "relation": "REPLACED_BY"
      },
      "basis": "CURATED",
      "reviewed": true
    },
    {
      "key": "NI_138",
      "act": "NI",
      "actName": "Negotiable Instruments Act, 1881",
      "section": "138",
      "title": "Dishonour of a cheque for insufficiency of funds",
      "description": "A cheque returned unpaid for want of funds or because it exceeds the arrangement. The complaint must follow a demand notice within 30 days of the return, and the drawer gets 15 days to pay. Punishable with up to two years, or a fine up to twice the cheque amount, or both. Very common and, on its own, usually a debt dispute rather than a mark of criminality.",
      "severity": "MODERATE",
      "severityBasis": null,
      "punishment": null,
      "maximumYears": null,
      "exposure": null,
      "death": false,
      "cognizable": false,
      "bailable": true,
      "commercial": true,
      "jurisdiction": "CENTRAL",
      "officialTitle": "Dishonour of cheque for insufficiency, etc., of funds in the account.",
      "officialSource": "https://indiacode.gov.in/handle/123456789/535883",
      "verifiedAt": "2026-10-17",
      "alsoKnownAs": null,
      "basis": "CURATED",
      "reviewed": true
    }
  ]
}

Read a court record's act text

Takes the acts field of a court record exactly as the court wrote it, for example "U/s 138 of N.I Act | Section 223BNSS", and returns what it means. It is the same reading that sets the risk level CasePrimus gives a case, so what it returns is what scored that case.

A line can name two acts at once and each is resolved. A section the catalogue does not hold is left out rather than guessed at. unmatched lists the lines in which nothing was recognised, so you can tell "this provision carries no penalty" from "we could not read your act text". Up to 50 lines per call.

Request URL

POSThttps://api.caseprimus.ai/api/caseprimus/v1/acts/sections/resolve

Request headers

TypeNameValue / descriptionOptional
StringContent-Typeapplication/jsonRequired
StringX-CasePrimus-Api-KeyYour API key: {apiKey}Required

No API key yet? See Authentication.

Input parameters

FieldDescription
acts
any
Required

The act-and-section lines from a court record, as a list of up to 50 or as one string.

Sample request

Request
BASE="https://api.caseprimus.ai/api/caseprimus/v1"

curl -X POST "$BASE/acts/sections/resolve" \
  -H "X-CasePrimus-Api-Key: $CASEPRIMUS_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "acts": [
      "U/s 138 of N.I Act | Section 223BNSS",
      "Totally Made Up Act 1999 | Section 7"
    ]
  }'

Responses

200What the lines mean.
400The request is not valid (60000).
403Caller lacks case.read, or the plan does not include this product (61470).

Response fields (HTTP 200)

FieldDescription
entries
array of object

Every provision recognised across all the lines, most serious first.

key
string

Stable id. Curated provisions keep a short key (NI_138); others are keyed by jurisdiction, act and section.

act
string

The act's short code where the catalogue has one, otherwise INDIA_CODE.

actName
string
section
string
title
string or null
description
string or null

What the section covers, in plain English. Absent where neither the catalogue nor the grading says anything the heading does not already say.

sectionText
string or null

The statute's OWN WORDS for this section, where India Code published the section as text rather than only as a heading - about two provisions in three, overwhelmingly state legislation (India Code serves central law section by section without the body). It is extracted from a published PDF, so the odd word is broken or a line runs on: it is the statute's wording, not a clean transcription of it, and `officialSource` is where to check it.

actContext
string or null

What this PART OF THE ACT covers. Written per act or per chapter, so every section under it carries the same sentence - read it alongside `description`, never instead of it. A provision with no description of its own often still has this, which is why it exists: it is the difference between telling a reader nothing about a section and telling them what kind of law it sits in.

descriptionBasis
enum or null

Where `description` came from. `CURATED` - written and checked by a person. `EXTERNAL_GRADED` - generated from the statute during the grading, and the weaker of the two. Null when there is no description at all; it never describes `actContext`, which is always act-level. Read it before quoting a description as authoritative.

CURATEDEXTERNAL_GRADED
severity
enum or null

Null where the provision states no punishment - a definition, a procedure, a repealed stub.

GRAVESERIOUSMODERATEMINORPROCEDURAL
severityBasis
enum or null

Set only where the severity was read from the section's own maximum punishment rather than written and checked by hand. Such a severity carries less weight in a risk level and can never on its own put a case in the top band. Null means a person wrote it down.

MAX_PUNISHMENT
punishment
string or null

The statute's own words that the severity rests on. The judgement is not checkable; the quote is.

maximumYears
number or null

The ceiling in years, where the clause states one.

death
boolean or null

Whether the provision reaches death or imprisonment for life, which no year count can express. Null where the grading recorded nothing either way, which is most provisions.

exposure
enum or null

What the section puts at stake financially. PROPORTIONATE has no ceiling - it is a multiple of the sum at issue.

PROPORTIONATECRORE_SCALETENS_OF_LAKHSLAKH_SCALEUNDER_1_LAKH
cognizable
boolean or null

Known only for hand-reviewed provisions.

bailable
boolean or null

Known only for hand-reviewed provisions.

commercial
boolean

Whether the provision is commercial rather than personal in character.

jurisdiction
string

CENTRAL, or the state whose legislation it is.

officialTitle
string or null

The heading as India Code prints it.

officialSource
string or null
verifiedAt
string or null

When this entry was last checked against India Code.

riskLevel
integer or null

How much litigation under this provision exposes a party, from 1 (least) to 5 (most), across the whole India Code corpus. Separate from `severity`, which measures the sentence the section carries: a provision can be a modest offence and still be a severe commercial exposure, which is why a dishonoured cheque is graded 5 here and moderate there. Where the two disagree this is the one that decides a case's risk level, except that it never lowers a severity a lawyer reviewed. Null where the provision is outside the graded corpus.

1 to 5

riskScore
integer or null

The same judgement on a finer scale, for sorting. Not a probability and not an amount.

0 to 100

riskBasisTier
enum or null

What the risk level rests on, which is the field to read before relying on one. `knowledge_reviewed` - graded from knowledge of what that act does; `signal` - a real offence or penalty clause was found in the section's own text; `reviewed_no_signal` - the text was read and carries no offence language; `admin` - an administrative or procedural heading; `uncertain` - only a heading was available, no statutory text, so the level is a triage estimate. A level on the `uncertain` tier carries reduced weight in a case's risk level.

true_content_groundedknowledge_reviewedsignalweb_reviewedreviewed_no_signaladminreasoned_uncertainuncertain
litigationCategory
string or null

What kind of dispute the provision gives rise to - for example CORPORATE, INSOLVENCY, TAX_INDIRECT, CRIM_ECON, LABOUR. Describes the provision, not a particular case. One of 25.

litigationCategoryLabel
string or null

The same category in words a person reads - "Economic / white-collar criminal offence" for CRIM_ECON. Published since; before that only the code was, and every screen that had it showed nothing rather than print an enum.

appliesTo
string or null

Who the provision exposes, as a short phrase from the grading's own vocabulary - "Companies", "Individuals, Businesses", "Employers, Employees" and so on, with a handful of older entries still reading `company`, `individual`, `both` or `state`. Not an enum worth relying on: a provision naming individuals can still matter to a company, since directors and officers are frequently named personally.

reviewedByLawyer
boolean

Whether a person wrote and checked this entry. Only these carry a severity that an automated grade is never allowed to lower.

alsoKnownAs
object or null

The same provision in the other code, and WHICH WAY ROUND - so an old citation reads "now BNS 318" and a new one "formerly IPC 420".

basis
enum

Where this provision came from, best attested first. CURATED - written and checked by hand against the statute. STATUTE - read by a model from India Code's own section-level text, with the punishment clause quoted. STATUTE_PDF - read the same way but from an act PDF that had to be split into sections first, for the ten states India Code publishes no sections for; same grading, weaker provenance. HEADING - India Code publishes the heading but the section states no punishment, so there is nothing to grade.

CURATEDSTATUTESTATUTE_PDFHEADING
reviewed
boolean

Whether a lawyer has checked this severity and description. True only for CURATED.

unmatched
array of string

The lines nothing was recognised in.

disclaimer
string
reviewed
boolean

Whether a lawyer has checked the severities and descriptions.

Response 200
{
  "entries": [
    {
      "key": "NI_138",
      "act": "NI",
      "actName": "Negotiable Instruments Act, 1881",
      "section": "138",
      "title": "Dishonour of a cheque for insufficiency of funds",
      "description": "A cheque returned unpaid for want of funds or because it exceeds the arrangement. The complaint must follow a demand notice within 30 days of the return, and the drawer gets 15 days to pay. Punishable with up to two years, or a fine up to twice the cheque amount, or both. Very common and, on its own, usually a debt dispute rather than a mark of criminality.",
      "severity": "MODERATE",
      "severityBasis": null,
      "punishment": null,
      "maximumYears": null,
      "exposure": null,
      "death": false,
      "cognizable": false,
      "bailable": true,
      "commercial": true,
      "jurisdiction": "CENTRAL",
      "officialTitle": "Dishonour of cheque for insufficiency, etc., of funds in the account.",
      "officialSource": "https://indiacode.gov.in/handle/123456789/535883",
      "verifiedAt": "2026-10-17",
      "alsoKnownAs": null,
      "basis": "CURATED",
      "reviewed": true
    },
    {
      "key": "BNSS_223",
      "act": "BNSS",
      "actName": "Bharatiya Nagarik Suraksha Sanhita, 2023",
      "section": "223",
      "title": "Examination of the complainant",
      "description": "Replaces CrPC 200; the accused must now be heard before cognizance is taken.",
      "severity": "PROCEDURAL",
      "severityBasis": null,
      "punishment": null,
      "maximumYears": null,
      "exposure": null,
      "death": false,
      "cognizable": null,
      "bailable": null,
      "commercial": false,
      "jurisdiction": "CENTRAL",
      "officialTitle": "Examination of complainant.",
      "officialSource": "https://indiacode.gov.in/handle/123456789/546323",
      "verifiedAt": "2026-10-17",
      "alsoKnownAs": {
        "key": "CRPC_200",
        "act": "CRPC",
        "section": "200",
        "title": "Examination of the complainant",
        "relation": "REPLACES"
      },
      "basis": "CURATED",
      "reviewed": true
    }
  ],
  "unmatched": [
    "Totally Made Up Act 1999 | Section 7"
  ],
  "disclaimer": "General information about what a section covers, not legal advice. Compiled for categorising litigation; the text of the statute and a qualified lawyer are the authority. The Bharatiya Nyaya Sanhita 2023, Bharatiya Nagarik Suraksha Sanhita 2023 and Bharatiya Sakshya Adhiniyam 2023 replaced the Indian Penal Code 1860, the Code of Criminal Procedure 1973 and the Indian Evidence Act 1872 with effect from 1 July 2024; a case filed before that date is still tried under the old section, so both are kept here and shown together. Where a section is marked \"from the statute\", its severity was read from that section's own maximum punishment and the words it was read from are shown beside it; such a severity should not be construed as a reviewed legal opinion, and never decides a high risk level on its own. State legislation is covered only where India Code publishes a statute section by section, which today means Maharashtra, Uttar Pradesh, Rajasthan, Jammu and Kashmir, Meghalaya, Telangana, Tamil Nadu, Uttarakhand, Jharkhand, Madhya Pradesh and the Andaman and Nicobar Islands; for other states, including Karnataka, Gujarat, Delhi, West Bengal and Bihar, India Code carries the acts but not their sections, so a case under them is reported with the court's own act text and no section description.",
  "reviewed": false
}

Severity and exposure

severity and exposure use these values. Both can be used as filters when you search.

FieldValues
severityGRAVE, SERIOUS, MODERATE, MINOR or PROCEDURAL
exposurePROPORTIONATE, CRORE_SCALE, TENS_OF_LAKHS, LAKH_SCALE or UNDER_1_LAKH
basisHow the provision was obtained: CURATED, STATUTE, STATUTE_PDF or HEADING

Two ways in

Search

Know what you are looking for

Use q for free text, section for a section number, and severity, exposure or jurisdiction to narrow the results. Results come most serious first unless you set sort.

Browse

Walk the catalogue

Take a jurisdiction from GET /acts/jurisdictions to GET /acts, then an act's name to GET /acts/sections?act=.... Use this when you do not know the act's name.

Resolve

Read a court record

POST /acts/sections/resolve takes the acts field of a court record as written. A line can name two acts at once and each is resolved, and unmatched lists the lines in which nothing was recognised.

Errors

Errors use the HTTP status and a JSON body with a stable numeric code. These are the errors documented for the Acts and Sections API. The full format, and the limits that apply to every call, are on Rate limits & errors.

StatusCodeMessage

Frequently asked questions

What is the difference between graded and ungraded provisions?

A graded provision carries a severity read from its own punishment clause. An ungraded one states no punishment, such as a definition or a procedural rule. Search returns graded provisions unless you set includeUngraded.

Does it cover state law as well as central law?

Yes. The catalogue covers central legislation and the legislation of the states. Set jurisdiction to CENTRAL or to a state's name to narrow a search.

Is this the same reading that sets a case's risk level?

Yes. The resolve endpoint calls the same reader that scores a case, so what it returns is what scored that case.

What if a section is not in the catalogue?

It is left out of the result rather than guessed at. The unmatched list names the lines in which nothing was recognised, so you can tell that a provision carries no penalty from not being able to read your act text.

How many lines can I resolve at once?

Up to 50 lines per call, sent as a list or as one string.

Is a provision's severity legal advice?

No. Severity and exposure are decision support to help your team review a case faster. Have a qualified person confirm anything you rely on.

How do I get an API key?

Create one from the Developer console in your CasePrimus.ai dashboard. Don't have an account yet? Request a demo and we will set you up.