Get District List

Endpoint Overview

GET /api/v1/land-verification/uttarakhand/meta/district-list

Description

The Uttarakhand District List API returns a complete list of all districts in the state of Uttarakhand, India. This metadata endpoint is a foundational utility within the Surepass Land Verification suite, enabling applications to populate district selection fields, validate user-submitted district names, and drive downstream land record queries specific to Uttarakhand.

By providing a standardized, up-to-date list of district names in the exact format expected by other land verification endpoints, this API eliminates hardcoding and ensures consistency across integrations.

Key Benefits

Standardized Data: Returns district names in the exact format required by other Surepass Uttarakhand land verification APIs, preventing mismatch errors.

Dynamic UI Population: Easily power dropdowns, autocomplete fields, or search filters in your application without maintaining a static list.

Single Source of Truth: Always reflects the authoritative list of Uttarakhand districts, reducing maintenance overhead.

Lightweight & Fast: A simple GET request with no body parameters — ideal for initialization calls on app load.

Use Cases

Real Estate

Banking & Finance

Legal & Compliance

Populate district dropdown menus in property listing and search forms to ensure valid input before submitting land record queries.

Validate district names provided by users or third-party data sources during property due diligence workflows.

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	No	Not required for this GET endpoint, but `application/json` is recommended.

Request Body

This endpoint does not require a request body.

Parameter	Type	Required	Description
—	—	—	No request body parameters are needed for this endpoint.

Example Request

{}

Process Response

Response Parameters

Parameter	Type	Description
data	array of strings	A list of all district names in Uttarakhand, in lowercase format.
status_code	integer	HTTP-equivalent status code for the response. `200` indicates success.
message_code	string	A machine-readable status indicator. `"success"` on successful responses.
message	string	A human-readable status message. `"Success"` on successful responses.
success	boolean	`true` if the request was processed successfully; `false` otherwise.

Example Successful Response

{
    "data": [
        "almora",
        "uttarkashi",
        "udham singh nagar",
        "chamoli",
        "champawat",
        "tehri garhwal",
        "dehradun",
        "nainital",
        "pithoragarh",
        "pauri garhwal",
        "bageshwar",
        "rudraprayag",
        "hardwar"
    ],
    "status_code": 200,
    "message_code": "success",
    "message": "Success",
    "success": true
}

Possible Error Responses

Unauthorized

Internal Server Error

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

Returned when the Authorization header is missing, malformed, or contains an invalid/expired JWT token. Ensure your Bearer token is valid and corresponds to the correct environment (sandbox or production).

Integration Best Practices

Security Recommendations

Never expose your JWT token in client-side code, public repositories, or logs. Store tokens securely using environment variables or a secrets manager.

Use environment-specific tokens: Always use the sandbox JWT token against the sandbox base URL and the production JWT token against the production base URL. Cross-environment usage will result in authentication errors.

Rotate tokens regularly and revoke any tokens that may have been compromised.

Transmit requests over HTTPS only to protect the Authorization header and response data in transit.

User Experience Guidelines

Cache the response on application startup or at a reasonable interval (e.g., daily) to avoid making redundant network calls each time a user loads a form — the district list is largely static.

Normalize user input against the returned list (case-insensitive comparison) before passing district values to downstream land verification endpoints, as the API returns district names in lowercase.

Display districts in a sorted or regionalized order in your UI for better usability, even though the API returns them in an unordered list.

Handle errors gracefully by falling back to a cached copy of the district list if the API is temporarily unavailable, ensuring uninterrupted user experience.

Code Samples

cURL

Python

Node.js

Related APIs

Uttarakhand Tehsil List — Retrieves the list of tehsils within a given Uttarakhand district, useful for cascading location selectors.

Uttarakhand Village List — Returns villages within a specified tehsil, enabling granular land record lookups.

Uttarakhand Land Record Verification — The primary land verification endpoint that uses district, tehsil, and village values to fetch and verify land ownership records.

Uttarakhand Khasra Details — Fetches plot-level (khasra) details for a specific land parcel identified by district, tehsil, village, and khasra number.

Compliance and Legal Considerations

Land record data in India is governed by state-specific land revenue laws, including the Uttarakhand Revenue Code. While this endpoint returns only metadata (district names) and does not expose any personally identifiable information (PII) or sensitive land records, downstream endpoints in the Land Verification suite may retrieve data that is subject to data privacy obligations. Ensure your use of land record data complies with applicable Indian laws, including the Digital Personal Data Protection Act (DPDPA), and that consent is obtained from individuals where required. Use the sandbox environment strictly for testing and development purposes — do not process real personal or property data in the sandbox environment.

Provide your bearer token in the

Authorization

header when making requests to protected resources.

Example:

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

{ "data": [ "almora", "uttarkashi", "udham singh nagar", "chamoli", "champawat", "tehri garhwal", "dehradun", "nainital", "pithoragarh", "pauri garhwal", "bageshwar", "rudraprayag", "hardwar" ], "status_code": 200, "message_code": "success", "message": "Success", "success": true }

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