Uttarakhand Land Verification

Endpoint Overview

POST /api/v1/land-verification/uttarakhand

Description

The Uttarakhand Land Record Verification API is the primary data retrieval endpoint of the Surepass Uttarakhand Land Verification suite. Given a fully specified location — district, tehsil, village, Fasli year range, and khata number — this endpoint fetches the complete land record for that khata from Uttarakhand's official revenue register, returning detailed owner information, individual plot (khasra) details, and a summary of total land holdings.

This is the culmination of the five-level metadata hierarchy (District → Tehsil → Village → Year → Khata). Where the metadata APIs help applications navigate to the right record, this endpoint delivers the actual land record content: who owns the land, which khasra numbers fall under the khata, the area of each plot, and aggregate land holding figures. The response includes owner names in both Hindi and transliterated English, making the data accessible for both vernacular and English-language applications.

Key Benefits

Comprehensive Record in a Single Call: Returns owner details, all associated khasra (plot) entries, and an aggregated land summary for a khata in one response, eliminating the need for multiple lookups.

Bilingual Owner Information: Provides owner names and related details in both Hindi (owner_name_hindi) and English transliteration (owner_name), supporting applications serving diverse user bases.

Plot-Level Granularity: Delivers individual khasra numbers, their associated year of land rights, and total area for each plot under the khata, enabling precise parcel-level analysis and verification.

Structured for Automation: The well-defined JSON response structure — with separate arrays for owner_details, orders_details, and land_details plus a land_summary object — makes it straightforward to parse, store, and process records programmatically at scale.

Use Cases

Real Estate

Banking & Finance

Legal & Compliance

Verify land ownership details and plot composition for a specific khata during property due diligence, confirming that the seller's claimed holdings match the official revenue record.

Display a buyer-facing ownership and land summary report in property transaction platforms, showing the owner name, all associated khasra numbers, individual plot areas, and total landholding in one consolidated view.

Technical Implementation

Authentication

All API requests require authentication using a JWT Bearer token. Authentication follows these steps:

Obtain API Credentials: Register with Surepass to receive your API key.

Generate JWT Token: Use your API key to generate a JWT token.

Include in Requests: Add the token to the Authorization header as Bearer TOKEN.

Different authentication tokens are used for sandbox and production environments:

Sandbox: https://sandbox.surepass.app

Production: https://kyc-api.surepass.app

Request Parameters

Request Headers

Header	Required	Description
Authorization	Yes	Bearer token for authentication. Format: `Bearer <JWT_TOKEN>`
Content-Type	Yes	Must be set to `application/json` as the endpoint expects a JSON request body.

Request Body

Parameter	Type	Required	Description
district	string	Yes	The name of the district in lowercase (e.g., `"almora"`). Obtain valid values from the Uttarakhand District List API.
tehsil	string	Yes	The name of the tehsil within the specified district, in lowercase (e.g., `"syalde"`). Obtain valid values from the Uttarakhand Tehsil List API.
village	string	Yes	The name of the village within the specified tehsil, in lowercase (e.g., `"ataliya"`). Obtain valid values from the Uttarakhand Village List API.
year	string	Yes	The Fasli year range for the land record (e.g., `"1411-1416"`). Obtain valid values from the Uttarakhand Year List API.
khata	string	Yes	The zero-padded khata number identifying the ownership account (e.g., `"00001"`). Obtain valid values from the Uttarakhand Khata List API.

Example Request

{
    "district": "almora",
    "tehsil": "syalde",
    "village": "ataliya",
    "year": "1411-1416",
    "khata": "00001"
}

Process Response

Response Parameters

Parameter	Type	Description
data	object	The root data object containing all land record details for the requested khata.
data.district	string	The district name as provided in the request, echoed back in the response.
data.tehsil	string	The tehsil name as provided in the request, echoed back in the response.
data.village	string	The village name as provided in the request, echoed back in the response.
data.year	string	The Fasli year range as provided in the request, echoed back in the response.
data.khata_no	string	The khata number as provided in the request, echoed back in the response.
data.owner_details	array of objects	A list of owner records associated with this khata. May contain one or more entries for co-owned land.
data.owner_details[].owner_name_hindi	string	The owner's name as recorded in the official revenue register, in Hindi script.
data.owner_details[].father_spouse_name	string	The name of the owner's father or spouse as recorded in the revenue register.
data.owner_details[].residence	string	The owner's recorded place of residence.
data.owner_details[].owner_name	string	The owner's name in transliterated English format.
data.orders_details	array	A list of orders or encumbrances associated with this khata. Returns an empty array if no orders are recorded.
data.land_details	array of objects	A list of individual khasra (plot) entries under this khata for the specified year.
data.land_details[].year_of_land_rights	string	The Fasli year in which the land rights for this khasra were established, as recorded in the revenue register (e.g., `"1374फ"`).
data.land_details[].khasra_number	string	The khasra (plot) number identifying this individual land parcel within the village (e.g., `"260"`, `"274म"`).
data.land_details[].total_area	string	The total area of this khasra plot, expressed as a decimal string in hectares (e.g., `"0.0160"`).
data.land_summary	object	An aggregate summary of all land records under this khata for the specified year.
data.land_summary.total_land_records	string	The total number of khasra entries recorded under this khata (e.g., `"40"`).
data.land_summary.total_land_area	string	The total combined area of all khasra plots under this khata, expressed as a decimal string in hectares (e.g., `"0.5200"`).
status_code	integer	HTTP-equivalent status code for the response. `200` indicates success.
success	boolean	`true` if the request was processed successfully; `false` otherwise.
message	string	A human-readable status message. `"Success"` on successful responses.
message_code	string	A machine-readable status indicator. `"success"` on successful responses.

Example Successful Response

{
    "data": {
        "district": "almora",
        "tehsil": "syalde",
        "village": "ataliya",
        "year": "1411-1416",
        "khata_no": "00001",
        "owner_details": [
            {
                "owner_name_hindi": "सा.नि.वि.",
                "father_spouse_name": ".",
                "residence": "नि. ग्राम",
                "owner_name": "Sa.Ni.Vi."
            }
        ],
        "orders_details": [],
        "land_details": [
            {
                "year_of_land_rights": "1374फ",
                "khasra_number": "260",
                "total_area": "0.0160"
            },
            {
                "year_of_land_rights": "1374फ",
                "khasra_number": "274म",
                "total_area": "0.0090"
            },
            {
                "year_of_land_rights": "1374फ",
                "khasra_number": "277",
                "total_area": "0.0180"
            },
            {
                "year_of_land_rights": "1374फ",
                "khasra_number": "287",
                "total_area": "0.0090"
            },
            {
                "year_of_land_rights": "1374फ",
                "khasra_number": "291",
                "total_area": "0.0200"
            },
            {
                "year_of_land_rights": "1374फ",
                "khasra_number": "263",
                "total_area": "0.0060"
            },
            {
                "year_of_land_rights": "1374फ",
                "khasra_number": "268",
                "total_area": "0.0110"
            },
            {
                "year_of_land_rights": "1374फ",
                "khasra_number": "266म",
                "total_area": "0.0310"
            }
        ],
        "land_summary": {
            "total_land_records": "40",
            "total_land_area": "0.5200"
        }
    },
    "status_code": 200,
    "success": true,
    "message": "Success",
    "message_code": "success"
}

Possible Error Responses

Unauthorized

Invalid Input

{
    "data": null,
    "status_code": 401,
    "success": false,
    "message": "Authentication credentials were not provided or are invalid.",
    "message_code": "unauthorized"
}

Returned when the Authorization header is missing, malformed, or contains an expired or invalid JWT token. Verify that you are using the correct Bearer token for the intended environment (sandbox or production) and that the token remains valid.

Integration Best Practices

Security Recommendations

Protect your JWT token rigorously: This endpoint returns real land ownership data including owner names in Hindi and English, residence details, and plot information. Store tokens exclusively in environment variables or a secrets manager — never in source code, client-side bundles, or application logs.

Use environment-specific tokens: The sandbox JWT token must only be paired with https://sandbox.surepass.app, and the production JWT token must only be paired with https://kyc-api.surepass.app. Cross-environment token use will result in authentication failures.

Apply access controls on your backend: Since the response contains personally identifiable landowner data, ensure that API calls are made server-side only and that the resulting records are accessible solely to authorized users within your system.

Rotate tokens regularly and revoke any token that may have been exposed through error logs, stack traces, or version control history.

User Experience Guidelines

Always use metadata API values as inputs: Never allow free-text entry for any of the five request parameters. Bind district, tehsil, village, year, and khata values directly to those returned by the respective upstream metadata APIs to guarantee valid inputs and prevent failed lookups.

Present bilingual owner names thoughtfully: Display owner_name_hindi as the primary name for Hindi-language users and owner_name (English transliteration) for English-language interfaces. Where both audiences are served, consider showing both side by side.

Handle empty orders_details gracefully: The orders_details array may be empty for many khata records. In your UI, either hide this section when empty or display a clear label such as "No orders or encumbrances recorded" rather than showing a blank field.

Display land_details and land_summary together: Present the individual khasra breakdown in a table alongside the land_summary totals so users can cross-check plot-level data against the aggregate at a glance.

Note the total_land_records vs. land_details count discrepancy: The land_summary.total_land_records field reflects the complete count of khasra entries in the official record, while land_details in the response may contain a subset. Inform users of this distinction in your UI where relevant.

Code Samples

cURL

Python

Node.js

Related APIs

Uttarakhand District List — Retrieves the complete list of districts in Uttarakhand. This is the first step in the metadata hierarchy and provides valid district values for this endpoint.

Uttarakhand Tehsil List — Returns all tehsils within a given district. This is the second step in the hierarchy and provides valid tehsil values for a selected district.

Uttarakhand Village List — Returns all villages within a given district and tehsil. This is the third step in the hierarchy and provides valid village values for this endpoint.

Uttarakhand Year List — Returns all available Fasli year ranges for a given village. This is the fourth step in the hierarchy and provides valid year values for this endpoint.

Uttarakhand Khata List — Returns all available khata numbers for a given village and year. This is the fifth and final metadata step, providing valid khata values required by this endpoint.

Compliance and Legal Considerations

This endpoint returns substantive land record data from Uttarakhand's official revenue registers, including personally identifiable information such as landowner names (in Hindi and English), residence details, and plot-level land holdings. Processing this data carries significant legal obligations. Ensure your application complies with the Digital Personal Data Protection Act (DPDPA), which governs the collection, processing, and storage of personal data in India. Obtain appropriate and explicit consent from individuals whose land records are being accessed, clearly state the purpose of data collection, and limit use strictly to those declared purposes. Land records in Uttarakhand are governed by the Uttarakhand Revenue Code; unauthorized commercial use or redistribution of revenue record data may constitute a legal violation. For applications in the financial sector, additionally ensure compliance with RBI guidelines on KYC and collateral verification. The sandbox environment must be used exclusively for development and testing with synthetic data — under no circumstances should real landowner or property data be submitted to or processed via the sandbox environment.

Provide your bearer token in the

Authorization

header when making requests to protected resources.

Example:

Authorization: Bearer ********************

Description#

Use Cases#

Technical Implementation#

Request Headers#

Request Body#

Example Request#

Response Parameters#

Example Successful Response#

Possible Error Responses#

Integration Best Practices#

Code Samples#

Request

Responses