Karnataka Land Verification

Endpoint Overview

POST /api/v1/land-verification/karnataka

Description

The Karnataka Land Verification API enables businesses and developers to programmatically retrieve official land records for properties located in Karnataka, India. By providing key location identifiers — district, taluka, hobli, village, and khata number — the API returns detailed land ownership information, area measurements, and associated tax/cess breakdowns sourced from Karnataka's official land records system (Bhoomi).

This API eliminates the need for manual verification at government offices, enabling real-time, automated due diligence during property transactions, loan disbursements, agricultural assessments, and KYC workflows. The response includes comprehensive details about individual land parcels including the hissa number, owner name, area dimensions, and a consolidated total summary.

Key Benefits

Instant Verification: Retrieve verified land records in real time without manual intervention or physical visits to government offices.

Structured Data: Receive detailed parcel-level breakdowns including area, tax components (local call, health care, vidya kara), and owner details in a clean, machine-readable format.

Dual Environment Support: Test seamlessly in the sandbox environment before going live in production with identical request/response schemas.

Fraud Prevention: Validate land ownership claims during loan origination, property purchases, or tenancy agreements to minimize risk of document fraud.

Use Cases

Banking & Finance

Real Estate & PropTech

Government & AgriTech

Verify land ownership and area details before approving agricultural or mortgage loans to ensure collateral authenticity.

Automate property due diligence during home loan processing to reduce turnaround time and operational costs.

Cross-check declared land assets during KYC and credit appraisal for rural borrowers.

Validate land records as part of MSME loan underwriting when land is offered as security.

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 <YOUR_JWT_TOKEN>.

Different authentication tokens are used for sandbox and production environments:

Sandbox: https://sandbox.surepass.app

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

⚠️ Never share your JWT token publicly or commit it to version control. Use environment variables to manage tokens securely.

Request Parameters

Request Headers

Header	Required	Description
`Authorization`	Yes	Bearer token in the format `Bearer <YOUR_JWT_TOKEN>`. Use the appropriate token for sandbox or production.
`Content-Type`	Yes	Must be set to `application/json`.

Request Body

Parameter	Type	Required	Description
`district`	string	Yes	The name of the district in Karnataka where the land is located (e.g., `"belagavi"`). Must be in lowercase.
`taluka`	string	Yes	The taluka (sub-district) within the specified district (e.g., `"chikkodi"`). Must be in lowercase.
`hobli`	string	Yes	The hobli (revenue circle) within the taluka (e.g., `"chikkodi"`). Must be in lowercase.
`village`	string	Yes	The name of the village within the hobli (e.g., `"chikkodi"`). Must be in lowercase.
`khata_no`	string	Yes	The khata number (account number) assigned to the land record in the village register (e.g., `"1"`). Provided as a string.

Example Request

Sandbox:

POST https://sandbox.surepass.app/api/v1/land-verification/karnataka

Production:

POST https://kyc-api.surepass.app/api/v1/land-verification/karnataka

{
    "district": "belagavi",
    "taluka": "chikkodi",
    "hobli": "chikkodi",
    "village": "chikkodi",
    "khata_no": "1"
}

Process Response

Response Parameters

Top-Level Fields

Parameter	Type	Description
`data`	object	The main response object containing land record details.
`status_code`	integer	HTTP status code of the response. `200` indicates success.
`success`	boolean	Indicates whether the request was successful (`true` or `false`).
`message`	string	Human-readable status message (e.g., `"Success"`).
`message_code`	string	Machine-readable status code (e.g., `"success"`).

`data` Object Fields

Parameter	Type	Description
`client_id`	string	A unique identifier for this verification request, generated by the system (e.g., `"karnataka_land_verification_mgGmDwfawOufvuyUlyov"`).
`district`	string	The district name as provided in the request.
`taluka`	string	The taluka name as provided in the request.
`hobli`	string	The hobli name as provided in the request.
`village`	string	The village name as provided in the request.
`khata_no`	string	The khata number as provided in the request.
`land_details`	array	An array of land parcel objects associated with the given khata number. Each object represents one hissa (sub-survey number).
`total_summary`	object	An aggregated summary of all land parcels listed under the khata number.

`land_details` Array — Individual Parcel Fields

Parameter	Type	Description
`order_number`	string	The sequential order number of the parcel entry within the khata record.
`hissa_number`	string	The hissa (survey sub-division) number of the land parcel (e.g., `"33/*/2 ಎ"`). May include Kannada script characters.
`owner_name`	string	The name of the registered owner of the land parcel as per official records.
`area`	string	The land area in standard Karnataka land measurement units (e.g., `"0.15.00.00"`).
`shape`	string	The shape-based tax component applicable to the parcel (e.g., `"0.23"`).
`local_call`	string	The local cess/tax component applicable to the parcel (e.g., `"0.12"`).
`health_care`	string	The health care cess component applicable to the parcel (e.g., `"0.03"`).
`vidya_kara`	string	The education cess (vidya kara) component applicable to the parcel (e.g., `"0.02"`).
`total`	string	The total tax/cess amount for the individual parcel (e.g., `"0.4"`).

`total_summary` Object Fields

Parameter	Type	Description
`total_area`	string	The aggregate land area across all parcels under the khata number.
`total_shape`	string	The aggregate shape tax across all parcels.
`total_local_call`	string	The aggregate local cess across all parcels.
`total_health_care`	string	The aggregate health care cess across all parcels.
`total_vidya_kara`	string	The aggregate education cess across all parcels.
`grand_total`	string	The total of all tax and cess components across all parcels under the khata.

Example Successful Response

{
    "data": {
        "client_id": "karnataka_land_verification_mgGmDwfawOufvuyUlyov",
        "district": "belagavi",
        "taluka": "chikkodi",
        "hobli": "chikkodi",
        "village": "chikkodi",
        "khata_no": "1",
        "land_details": [
            {
                "order_number": "1",
                "hissa_number": "33/*/2 ಎ",
                "owner_name": "Alase Prakasha Shantinatha",
                "area": "0.15.00.00",
                "shape": "0.23",
                "local_call": "0.12",
                "health_care": "0.03",
                "vidya_kara": "0.02",
                "total": "0.4"
            }
        ],
        "total_summary": {
            "total_area": "0.15.00.00",
            "total_shape": "0.23",
            "total_local_call": "0.12",
            "total_health_care": "0.03",
            "total_vidya_kara": "0.02",
            "grand_total": "0.4"
        }
    },
    "status_code": 200,
    "success": true,
    "message": "Success",
    "message_code": "success"
}

Possible Error Responses

Unauthorized (401)

Invalid Input (400)

Record Not Found (404)

{
    "data": null,
    "status_code": 401,
    "success": false,
    "message": "Unauthorized access. Invalid or missing Bearer token.",
    "message_code": "unauthorized"
}

This error occurs when the Authorization header is missing, the JWT token is malformed, or the token has expired. Ensure that a valid Bearer token for the correct environment (sandbox or production) is included in the request header.

Integration Best Practices

Security Recommendations

Store tokens securely: Always store JWT Bearer tokens in environment variables or a secrets manager. Never hardcode tokens in source code or expose them in client-side applications.

Use HTTPS only: All API calls must be made over HTTPS. Never transmit tokens or land record data over unencrypted connections.

Rotate tokens regularly: Periodically regenerate your API credentials and update tokens in your systems to minimise the risk of unauthorised access.

Restrict token scope: If your platform allows scoped tokens, use tokens with the minimum permissions required for land verification workflows only.

Validate responses: Always check the success field and status_code in the response before processing the data payload to handle errors gracefully.

User Experience Guidelines

Handle Kannada script gracefully: The hissa_number field may contain Kannada script characters (e.g., ಎ). Ensure your frontend and database layer support UTF-8 encoding to display and store these values correctly.

Display summary prominently: Surface the total_summary object alongside individual land_details to give users an at-a-glance overview before drilling into parcel-level data.

Provide clear error messages: Translate message_code values into user-friendly messages in your application UI to help users understand and resolve input errors quickly.

Use sandbox for testing: Always test your integration end-to-end in the sandbox environment (https://sandbox.surepass.app) before switching to production to avoid unintended costs or disruptions.

Show client_id for support: Expose the client_id from the response in your internal logs or support tooling to facilitate quick debugging with the Surepass team if issues arise.

Code Samples

cURL

Python

Node.js

Compliance and Legal Considerations

Data Privacy: Land record data retrieved via this API includes personal information such as owner names. Ensure your application complies with applicable data protection regulations, including India's Digital Personal Data Protection Act (DPDP Act, 2023), before storing or processing this data.

Authorised Use Only: This API is intended for lawful purposes such as loan processing, property due diligence, and government scheme verification. Unauthorised bulk scraping or use of land records for commercial resale without explicit consent may violate applicable laws.

Official Source Dependency: Land record data is sourced from Karnataka's Bhoomi system. Record availability, accuracy, and timeliness are subject to the completeness and currency of the underlying government database.

Audit Trails: Maintain logs of all land verification queries including the client_id returned in each response. This supports audit requirements in regulated industries such as banking and insurance.

No Legal Warranty: The data returned by this API reflects information available in the government land records system and should not be construed as a legal title opinion or ownership guarantee. Always consult a qualified legal professional for property transactions requiring title assurance.

Provide your bearer token in the

Authorization

header when making requests to protected resources.

Example:

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

curl --location --request POST 'https://kyc-api.surepass.app/api/v1/land-verification/karnataka' \ --header 'Authorization: Bearer <token>' \ --header 'Content-Type: application/json' \ --data-raw '{ "district": "belagavi", "taluka": "chikkodi", "hobli": "chikkodi", "village": "chikkodi", "khata_no": "1" }'

{ "data": { "client_id": "karnataka_land_verification_mgGmDwfawOufvuyUlyov", "district": "belagavi", "taluka": "chikkodi", "hobli": "chikkodi", "village": "chikkodi", "khata_no": "1", "land_details": [ { "order_number": "1", "hissa_number": "33/*/2 ಎ", "owner_name": "Alase Prakasha Shantinatha", "area": "0.15.00.00", "shape": "0.23", "local_call": "0.12", "health_care": "0.03", "vidya_kara": "0.02", "total": "0.4" } ], "total_summary": { "total_area": "0.15.00.00", "total_shape": "0.23", "total_local_call": "0.12", "total_health_care": "0.03", "total_vidya_kara": "0.02", "grand_total": "0.4" } }, "status_code": 200, "success": true, "message": "Success", "message_code": "success" }

Description#

Use Cases#

Technical Implementation#

Request Headers#

Request Body#

Example Request#

Response Parameters#

Top-Level Fields#

data Object Fields#

land_details Array — Individual Parcel Fields#

total_summary Object Fields#

Example Successful Response#

Possible Error Responses#

Integration Best Practices#

Code Samples#

Request

Responses