Court Records Verification API
Find the civil and criminal court cases of a person or a business, with each case’s court, status and next hearing, in one asynchronous API.
The documentation opens in the VerifyAll dashboard after sign-in, for accounts with approved API access. New to the API? Start with the developer guide.
Overview
What the Court Records Verification API does
The Court Records Verification API searches court records for cases involving a person or a business and returns a structured report: an overall result, a risk level, and every case counted as the subject’s with its court, case type, status, next hearing, acts and sections, and which side the subject is on.
An individual check takes name, father’s name, date of birth and address. A business check takes the company name, legal form, registered address and directors, and lists each director’s cases separately from the company’s. District, state, earlier addresses and other spellings of the name help match cases to the right subject.
Hiring, lending and vendor teams use it where a court case changes the decision: a pending criminal case on a hire, a recovery suit against a borrower, a dispute with a supplier. The call returns a record id at once and you read the report back when it is complete.
How it works
- 1
Call GET /crime/input-requirements once to see which fields an individual or business check needs on your account, then send POST /crime/create with subject_type, those fields and the consent object.
- 2
The request is checked before anything is charged. It is accepted with outcome pending and a data.id, and charged once from your prepaid wallet; if the search cannot be placed, the charge is refunded.
- 3
The search finishes later, from minutes to a few business days. Poll GET /crime/list for the status, or add a webhook endpoint in the dashboard to receive check.completed or check.failed.
- 4
Read the report with GET /crime/list/{id} (add include_probable=true for probable matches) and download the PDF with POST /pdf-reports/legal-individual or legal-business using the record id.
Request and response
Court records verification API endpoints and fields
The main fields; the full reference with every field, error code and a cURL sample is in the dashboard docs.
| Endpoint | What it does |
|---|---|
| GET/crime/input-requirements | The fields an individual or business check needs, and whether they are enforced |
| POST/crime/create | Start a court records search on a person or a business |
| GET/crime/list | Your legal checks with status, risk level and case count (Production key) |
| GET/crime/list/{id} | Read a completed court records report (Production key) |
| DELETE/crime/delete/{id} | Delete a legal check and its report (Production key) |
Request fields
| Field | What it is |
|---|---|
| subject_typeRequired | individual for a person, business for a company, firm or proprietorship. |
| name / father_name / dobOptional | Individual: full name, father’s (or husband’s or wife’s) name and date of birth (YYYY-MM-DD, at least 18 years old). |
| addressOptional | The person’s current address, or the business’s registered address, as one line. |
| company_name / company_typeOptional | Business: registered name and legal form (private_limited, public_limited, llp, proprietorship, registered_partnership and others). |
| directorsOptional | Business: up to 10 directors, partners or the proprietor, each with name, father_name and address. |
| city / district / stateOptional | Where the address is. District and state help confirm which cases belong to the subject. |
| past_addresses / aliases / spouse_nameOptional | Earlier addresses, other names and the spouse’s name. |
| pan / cin / gstin / former_namesOptional | Optional identifiers and earlier business names. |
| consentRequired | obtained: true and a purpose of up to 200 characters. |
| client_refOptional | Your reference, stored with the check. |
What the answer returns
| Field | What it is |
|---|---|
| overall | clear (nothing found), cases_found, or unresolved (no case counted, but same-name cases could not be ruled out; not a pass). |
| risk_level | The most severe level among the cases: none, low, medium or high. |
| total_cases / cases_by_court_level | Cases counted as the subject’s, and how many sit at each court level. |
| cases | Each case: cnr, case_number, court_name, court_level, district, case_category (civil or criminal), case_type, status, filed_on, next_hearing_on, acts_and_sections. |
| cases[].subject_side | petitioner (the subject filed it), respondent (the case is against the subject) or not_a_party. |
| director_checks | Business reports: each director’s own cases, counted there and not in total_cases. |
| probable_matches | With include_probable=true: cases with a match_score of 50 or more that could not be confirmed as the subject’s, never counted. |
| limitations / as_of | What the report does not cover, as sentences to show with the result, and the date the court records were read. |
Base URL https://api.verifyall.ai. Authenticate with the X-API-Key header (a va_sandbox_ or va_live_ key). Every answer carries data, status_code, success, message and message_code; checks add outcome, checkResultId, charged and charged_amount.
Key features
Court Records Verification API features and capabilities
Match scoring you can explain
A case is counted as the subject’s only from a match_score of 70 with a detail that identifies them; 50 to 69 is a probable match you can ask for separately.
Unresolved is never a pass
When same-name cases cannot be ruled out, overall is unresolved and unresolved is true, so your workflow can send the case for review instead of clearing it.
Directors searched with the business
A business check covers the company and its directors, partners or proprietor in one request, with the directors’ cases kept apart from the company’s own.
Inputs checked before you pay
GET /crime/input-requirements tells your form what to collect, and a request missing an enforced field is refused before any charge.
Use cases
Where businesses use the Court Records Verification API
Pre-employment screening
Check a candidate for pending criminal cases before an offer, especially for roles with cash, data or customer access.
Borrower due diligence
See recovery suits, cheque bounce cases and other litigation against an applicant or a borrowing company before sanction.
Vendor and distributor onboarding
Search a supplier and its directors for disputes and criminal cases before signing a contract.
Tenant and partner checks
Screen tenants, franchisees and channel partners where a court history affects the agreement.
Industries
Coverage
Court cases of individuals, and of businesses with their directors, in India, at district court, tribunal, High Court and Supreme Court level.
Limitations to plan for
- Results depend on the details you send. Without a father’s name, district or date of birth, more results can come back unresolved.
- A completed search can take from minutes to a few business days; do not hold a real-time journey on it.
- Each report lists its own limitations; show them with the result. The colour coding is a display aid, not a legal conclusion.
- Listing, reading and deleting checks work with the Production key only. A Sandbox check returns a sample report, read through the results history.
Integration
How to integrate the Court Records Verification API
From a business account to your first live call.
Step 1
Create a business account on VerifyAll and get it approved, as for running checks in the dashboard.
Step 2
Request Developer API access under Developers in the dashboard: the APIs you need, your expected monthly volume and your use case. The VerifyAll team reviews it and shares the API Services Agreement.
Step 3
Once the agreement is signed and access is approved, create your Sandbox key and build against sample data. Sandbox calls are never charged.
Step 4
Create your Production key, recharge your wallet and switch the key in your code: the endpoint and fields stay the same.
Get started
Request access to the Court Records Verification API
Tell us what you want to verify. We reply within one business day with access steps, Sandbox details and your API pricing.
View API documentation
The full reference for Court Records Verification API (endpoints, fields, errors, cURL) opens in the dashboard once your access is approved.
Open the docs (sign-in)Create a business account
API keys are issued to an approved business account. Sign up, then request access under Developers.
Create account
Pricing
Production calls are charged per check from your prepaid VerifyAll wallet, at your account’s API price; GST is added separately when you recharge. Sandbox calls are never charged. Your API prices are shown in the dashboard once access is approved. How pricing works
Already have a business account? Sign in to request access
Court Records Verification API: frequently asked questions
Answers for teams planning an integration.
Still have questions? Our team is happy to help.
Contact SupportRelated APIs
AML Screening API
LiveInstant answerScreen a person or an entity against sanctions, enforcement and regulatory watch lists and adverse media in one call, with every hit scored.
View API detailsCourt Case Watch API
LiveInstant answerKeep following the pending cases of a court records report for 12 months, and hear about each new hearing date, change and disposal.
View API detailsBackground Verification API
LiveFinishes laterRun the background checks you choose on one person in a single request, and read back one report with an overall result and every check’s outcome.
View API detailsCIN Verification API
LiveInstant answerSend a Corporate Identification Number and get the company’s name, status, capital, address and compliance dates back in one call.
View API details
All legal and AML APIsRun Court records verification in the dashboard, without codeBrowse the API Marketplace
Start with the Court Records Verification API
Request access, build against the Sandbox, then go live with your Production key.