> ## Documentation Index > Fetch the complete documentation index at: https://docs-neevlegal.neeved.com/llms.txt > Use this file to discover all available pages before exploring further. # Get full case details by CNR number > Returns the complete case record for a single CNR number, including all parties, hearing schedule, legal references, and hearing history. ## OpenAPI ````yaml post /case-detail/searchByCnr openapi: 3.0.3 info: title: NeevLegal API description: >- The NeevLegal REST API provides structured, programmatic access to Indian court case data. Search cases, retrieve full case records by CNR number, and explore the court directory across district courts, high courts, and the Supreme Court of India. version: 1.0.0 servers: - url: https://api-neevlegal.neeved.com/api/v1 description: Version 1 security: [] tags: - name: Case Detail description: Retrieve the complete case record for one or more CNR numbers. - name: Case Search description: >- Search across district courts, high courts, and the Supreme Court by party name, advocate, judge, FIR number, or other criteria. - name: Court Structure description: >- Browse the Indian court directory — states, districts, court complexes, and individual courts. paths: /case-detail/searchByCnr: post: tags: - Case Detail summary: Get full case details by CNR number description: >- Returns the complete case record for a single CNR number, including all parties, hearing schedule, legal references, and hearing history. requestBody: required: true content: application/json: schema: type: object properties: cnrNumber: type: string description: >- The 16-character Case Number Register identifier of the case to retrieve. minLength: 16 maxLength: 16 pattern: ^[A-Z]{4}[A-Z0-9]{2}\d{10}$ required: - cnrNumber responses: '200': description: Case found content: application/json: schema: type: object properties: success: type: boolean example: true response: type: object properties: data: type: object description: The full case record. properties: cnrNumber: type: string description: >- The 16-character Case Number Register identifier. Uniquely identifies the case across all Indian district courts. Format: 4-character court code + 2 alphanumeric characters + 10 digits. example: MHPN010123456789 caseStatus: type: string description: >- Current lifecycle state of the case. Pending means the case is still being heard; Disposed means it has been concluded. enum: - Pending - Disposed court: type: object description: >- Identifies the court where this case is filed and being heard. properties: stateName: type: string description: Full name of the state. example: Maharashtra stateCode: type: string description: >- Two-letter state code used in court identifiers and NeevLegal API path parameters. example: MH districtName: type: string description: Full name of the district. example: Pune districtCode: type: string description: >- District identifier used in court structure lookups. example: PUNE complexName: type: string description: Name of the court complex building or campus. complexCode: type: string description: Unique identifier for the court complex. courtName: type: string description: >- Name of the individual court or bench within the complex. courtNumber: type: string description: Court room or court number within the complex. required: - stateName - stateCode - districtName - districtCode - complexName - complexCode - courtName - courtNumber judgeName: type: string nullable: true description: >- Name of the presiding judge as recorded on the case. Null if not yet assigned. example: Hon'ble Shri M. Rajendar Reddy petitioners: type: array description: Parties appearing on the filing side of the case. items: type: object properties: partyName: type: string nullable: true description: >- Full name of the party as recorded by the court. example: John Doe advocateName: type: string nullable: true description: >- Name of the advocate representing this party. example: Adv. Jane Smith partyType: type: string nullable: true description: Role label assigned by the court registry. example: Petitioner required: - partyName - advocateName - partyType respondents: type: array description: Parties on the opposing side of the case. items: type: object properties: partyName: type: string nullable: true description: >- Full name of the party as recorded by the court. example: Jane Doe advocateName: type: string nullable: true description: >- Name of the advocate representing this party. example: Adv. John Smith partyType: type: string nullable: true description: Role label assigned by the court registry. example: Respondent required: - partyName - advocateName - partyType nextHearingDate: type: string nullable: true description: >- Date on which this case is next scheduled to be heard. Format: DD-MM-YYYY. Use this field to drive hearing alerts and calendar integrations. nextHearingPurpose: type: string nullable: true description: >- The stated purpose for the next scheduled hearing — for example, Arguments, Evidence, or Judgment. firstHearingDate: type: string nullable: true description: >- Date on which the case was first called before the court. Format: DD-MM-YYYY. caseType: type: string description: >- Abbreviated case type code used by the court — for example, CS (Civil Suit), CC (Criminal Complaint), WP (Writ Petition). example: CS caseNumber: type: string description: >- The display case number in the format Type/Serial/Year. example: CS/12/2023 filingDate: type: string description: >- Date the case was originally submitted to the court. Format: DD-MM-YYYY. example: 01-01-2023 filingNumber: type: string nullable: true description: >- Provisional number assigned at the time of submission, before the court formally registers the case. registrationNumber: type: string nullable: true description: >- Official number assigned when the court formally accepted and registered the case. registrationDate: type: string nullable: true description: >- Date the case was formally registered by the court. Format: DD-MM-YYYY. decisionDate: type: string nullable: true description: >- Date on which the case was decided or disposed of. Null when caseStatus is Pending. natureOfDisposal: type: string nullable: true description: >- How the case was concluded — for example, Decreed, Dismissed, Settled, or Withdrawn. Present only when caseStatus is Disposed. category: type: string nullable: true description: >- Subject category under which the court registry has classified this case. subCategory: type: string nullable: true description: >- More detailed sub-classification within the parent category. subject: nullable: true description: Reserved for future use. acts: type: array description: Statutes and provisions invoked in this case. items: type: object properties: act: type: string nullable: true description: Name of the statute or legislation. section: type: string nullable: true description: Section or provision of the statute. required: - act - section stage: nullable: true description: >- Procedural stage of the case. Reserved for future use. hearingHistory: type: array nullable: true description: Chronological log of past hearings for this case. items: type: object properties: hearingDate: type: string nullable: true description: >- Date this hearing took place. Format: DD-MM-YYYY. example: 15-01-2024 purpose: type: string nullable: true description: >- Business of the day — the purpose for which the case was listed at this hearing. example: Arguments nextDate: type: string nullable: true description: >- The next date given at this hearing. Format: DD-MM-YYYY. example: 20-02-2024 judge: type: string nullable: true description: >- Name of the judge who presided at this hearing. orderUrl: type: string nullable: true description: >- URL of the order or judgment passed at this hearing. Null if no order was passed. required: - hearingDate - purpose - nextDate - judge - orderUrl firDetails: type: object nullable: true description: >- First Information Report reference. Present only for criminal cases; null for civil matters. properties: firNumber: type: string nullable: true description: >- FIR registration number assigned by the police station. policeStation: type: string nullable: true description: >- Name of the police station where the FIR was lodged. year: type: string nullable: true description: Year in which the FIR was registered. required: - firNumber - policeStation - year lowerCourtDetails: type: object nullable: true description: >- For High Court cases: reference to the lower court or tribunal from which this matter originated. properties: courtName: type: string nullable: true description: >- Name of the originating lower court or tribunal. caseNumber: type: string nullable: true description: Case number as assigned by the lower court. decisionDate: type: string nullable: true description: >- Date of the lower court decision that gave rise to this matter. decision: type: string nullable: true description: >- Outcome or disposition at the lower court level. required: - courtName - caseNumber - decisionDate - decision linkedCases: type: array nullable: true description: >- Other cases formally linked or clubbed with this one by the court. items: type: object additionalProperties: {} transferDetails: nullable: true description: >- Transfer history for cases moved between courts. Reserved for future use. lastUpdated: type: string description: >- ISO 8601 timestamp of the most recent NeevLegal data sync for this case. Compare against your own cached timestamp to determine whether a refresh is needed. example: '2024-01-15T10:30:00.000Z' required: - cnrNumber - caseStatus - court - judgeName - petitioners - respondents - nextHearingDate - nextHearingPurpose - firstHearingDate - caseType - caseNumber - filingDate - filingNumber - registrationNumber - registrationDate - decisionDate - natureOfDisposal - category - subCategory - subject - acts - stage - hearingHistory - firDetails - lowerCourtDetails - linkedCases - transferDetails - lastUpdated required: - data required: - success - response '400': description: Validation error — cnrNumber failed format validation content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' '401': description: Missing or invalid API key content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' '404': description: No case found for the given CNR number content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' security: - apiKeyAuth: [] components: schemas: ErrorResponse: type: object description: Standard error envelope returned on all non-2xx responses. properties: success: type: boolean description: Always false for error responses. example: false message: type: string description: Human-readable description of what went wrong. example: API key not found or has been revoked. moreInfo: type: string description: Additional context when available. example: No additional info found. required: - success - message - moreInfo securitySchemes: apiKeyAuth: type: apiKey in: header name: X-API-Key ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.