Uttarakhand Land Verification

Overview

The Uttarakhand Land Verification APIs provide a structured, programmatic interface to Uttarakhand's official revenue land records, enabling applications to navigate the state's administrative land hierarchy and retrieve authoritative ownership and plot-level data for any khata (ownership account) across all districts. Designed for financial institutions, real estate platforms, legal services, and compliance teams, this category delivers the data infrastructure needed to verify land ownership, assess property collateral, and conduct due diligence against official government records — all through a consistent, developer-friendly API suite.

Category Details

Parent Category: Land Verification
Child Categories: Uttarakhand Land Verification
APIs in this category: Get District List, Tehsil List, Village List, Year List, Khata List, Uttarakhand Land Verification

Key Capabilities

Main Functionality

The Uttarakhand Land Verification API category provides end-to-end access to Uttarakhand's revenue land records through a five-level guided metadata hierarchy — district, tehsil, village, year, and khata — culminating in a comprehensive land record retrieval endpoint. Together, these APIs enable applications to dynamically navigate administrative boundaries, identify the correct record context, and retrieve verified ownership details, khasra-level plot data, and aggregate land holding summaries for any location in the state.

Hierarchical Location Navigation

Five dedicated metadata APIs — District List, Tehsil List, Village List, Year List, and Khata List — form a sequential, cascading navigation chain. Each level uses the output of the previous to scope its results, ensuring applications always work with valid administrative identifiers at every step before fetching actual land records. This hierarchy mirrors Uttarakhand's official revenue administration structure and prevents invalid or mismatched record queries.

Authoritative Land Record Retrieval

The Uttarakhand Land Verification endpoint retrieves complete, official land records for a specified khata from the state revenue register. The response encompasses owner details in both Hindi and English, a full breakdown of associated khasra (plot) numbers with individual areas and year of land rights, any recorded orders or encumbrances, and an aggregate land summary — providing everything needed for ownership verification in a single API call.

Bilingual and Structured Data Output

All land record responses are returned in clean, structured JSON with owner names provided in both Hindi script and English transliteration. This makes the data immediately usable across Hindi-language and English-language application interfaces, as well as in automated processing pipelines that require machine-readable, consistently formatted output without manual post-processing.

Common Use Cases

Real Estate

Banking & Finance

Legal & Compliance

Power end-to-end property verification workflows in real estate platforms, guiding users through district → tehsil → village → year → khata selection and delivering official ownership and plot records to support informed buying decisions.

Validate ownership claims and detect discrepancies between seller-stated and officially recorded land holdings during title due diligence, using khasra-level area data and owner details from the revenue register.

Integration Considerations

Best Practices

Always traverse the metadata hierarchy in sequence: Use the District List → Tehsil List → Village List → Year List → Khata List APIs in order to obtain valid input values at each level. Never allow free-text input for location parameters — always bind them to values returned by the upstream metadata API.

Cache metadata API responses: District, tehsil, village, year, and khata lists are stable administrative data that changes infrequently. Cache responses at each level — keyed by the relevant upstream identifiers — to reduce redundant API calls and improve application performance.

Use environment-specific JWT tokens: Always pair your sandbox JWT token exclusively with the sandbox base URL (https://sandbox.surepass.app) and your production JWT token with the production base URL (https://kyc-api.surepass.app). Cross-environment token use will cause authentication failures.

Handle bilingual data thoughtfully: The land record response provides owner_name_hindi and owner_name (English transliteration) for each owner. Design your data models and UI to accommodate both fields rather than discarding either, as the Hindi name is the authoritative record value.

Process orders_details defensively: This array may be empty for most records. Ensure your parsing logic handles an empty array gracefully rather than treating it as an error condition.

Important Limitations

Sequential dependency: The land record verification endpoint requires all five location parameters (district, tehsil, village, year, khata) to be valid and consistent with each other. Passing values from mismatched levels of the hierarchy — or values not sourced from the metadata APIs — will result in failed record lookups.

Fasli year format: Year values must be supplied in the exact format returned by the Year List API (e.g., "1411-1416" or "999"). The API does not accept Gregorian calendar years or alternative Fasli year formats.

Khata number format: Khata numbers must be supplied as zero-padded strings in the exact format returned by the Khata List API (e.g., "00001"). Integer or non-padded formats may not be recognized.

Sandbox for testing only: The sandbox environment is strictly for development and integration testing. Do not submit real personal data, live land ownership queries, or production property records to the sandbox under any circumstances.

Data reflects official revenue records: Land record data is sourced from Uttarakhand's official revenue register. Any discrepancies between official records and actual ground conditions are outside the scope of this API and should be addressed through the appropriate state revenue authority.

How APIs in this Category Work Together

The six APIs in the Uttarakhand Land Verification category are designed as a tightly coupled, sequential workflow rather than independent standalone endpoints. The five metadata APIs form a progressive filtering chain that narrows the administrative scope from state-level districts down to individual ownership accounts, with each API's output serving directly as the input to the next. Only once a valid khata number has been identified through this chain does the land record verification endpoint become callable with confidence.

Key Integration Patterns:

District List + Tehsil List: The district name returned by the District List API is passed directly as the district parameter to the Tehsil List API, scoping tehsil results to only those within the selected district.

Village List + Year List: The village name from the Village List API, combined with district and tehsil, is passed to the Year List API to retrieve only the Fasli year ranges for which records exist in that specific village — preventing queries against non-existent record periods.

Khata List + Uttarakhand Land Verification: The khata number from the Khata List API is the final input needed to call the land record verification endpoint, which returns the complete ownership record, khasra breakdown, and land summary for that khata.

A complete end-to-end integration begins with a call to the District List API on application initialization to populate the district selector. When a user selects a district, the Tehsil List API is called to populate tehsils; tehsil selection triggers the Village List call; village selection triggers the Year List call; and year selection triggers the Khata List call. With a khata selected, the application has all five required parameters and can call the Uttarakhand Land Verification endpoint to retrieve the full land record. This guided flow ensures every parameter is valid at every step, and caching responses at each level — keyed by the upstream selection — minimizes API calls while maintaining a responsive user experience across the full workflow.

The Uttarakhand Land Verification category is part of the broader Land Verification suite within the Surepass platform, which provides state-specific land record access across multiple Indian states. Each state-level land verification category follows a similar hierarchical metadata pattern but operates against its own state revenue system with state-specific administrative identifiers, year formats, and record structures. Teams building multi-state property verification solutions will work across several such categories in parallel, using the same integration patterns established here.

Related Categories include:

Land Verification (Parent Category): The umbrella category encompassing all state-specific land record verification APIs on the Surepass platform, of which Uttarakhand Land Verification is one node. Teams needing land verification across multiple Indian states will use this parent category to discover and access other state-specific suites.

KYC Verification: Land records often contain owner names that need to be cross-referenced against identity documents. KYC Verification APIs complement land record data by enabling owner name and identity validation as part of a comprehensive property and borrower due diligence workflow.

Business Verification: For land holdings held by companies, trusts, or other legal entities rather than individuals, Business Verification APIs can be used alongside land record data to verify the legal status and ownership structure of the entity named in the revenue record.

When combined, these related categories enable fully integrated property and identity verification pipelines. For example, a lender assessing a land-backed loan application in Uttarakhand might use the Uttarakhand Land Verification APIs to retrieve official ownership and plot data, cross-reference the owner's name and identity using KYC Verification APIs, and — if the applicant is a business entity — validate the company's legal status through Business Verification APIs. This multi-category approach ensures that property, identity, and entity verification are conducted cohesively within a single platform rather than across disparate third-party data sources.

Overview#

Key Capabilities#

Common Use Cases#

Integration Considerations#

How APIs in this Category Work Together#

Related Categories#

Overview

Key Capabilities

Common Use Cases

Integration Considerations

How APIs in this Category Work Together

Related Categories