Feel free to reach techsupport@surepass.io for any technical support or guidance.
Authorization header as Bearer TOKEN.https://sandbox.surepass.apphttps://kyc-api.surepass.app| Header | Required | Description |
|---|---|---|
| Authorization | Yes | Bearer token for authentication. Format: Bearer <JWT_TOKEN> |
| Content-Type | Yes | Must be set to application/json since a JSON request body is required. |
| Parameter | Type | Required | Description |
|---|---|---|---|
| district | string | Yes | The name of the district for which tehsils should be retrieved. Must be a valid Uttarakhand district name in lowercase (e.g., "almora"). Use the Uttarakhand District List API to obtain valid district values. |
{
"district": "almora"
}| Parameter | Type | Description |
|---|---|---|
| data | object | Contains the district name and its associated tehsil list. |
| data.district | string | The district name as provided in the request, echoed back in the response. |
| data.tehsil_list | array of strings | A list of all tehsil names within the specified district, returned 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. |
{
"data": {
"district": "almora",
"tehsil_list": [
"almora",
"chaukhutiya",
"jaleli",
"jainti",
"dwarahat",
"bagwalipokher",
"bhanoli",
"bhikiyasain",
"machhor",
"ranikhet",
"lamgara",
"sult",
"someshwar",
"syalde"
]
},
"status_code": 200,
"message_code": "success",
"message": "Success",
"success": true
}{
"data": null,
"status_code": 401,
"message_code": "unauthorized",
"message": "Authentication credentials were not provided or are invalid.",
"success": false
}Authorization header is missing, malformed, or contains an invalid or expired JWT token. Verify that your Bearer token is correct and that you are using the token corresponding to the intended environment (sandbox or production).https://sandbox.surepass.app) and the production JWT token with the production base URL (https://kyc-api.surepass.app). Mixing tokens across environments will cause authentication failures.tehsil_list — this creates an intuitive, error-free location selection flow.curl --location --request POST 'https://kyc-api.surepass.app/api/v1/land-verification/uttarakhand/meta/tehsil-list' \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data-raw '{
"district": "almora"
}'{
"data": {
"district": "almora",
"tehsil_list": [
"almora",
"chaukhutiya",
"jaleli",
"jainti",
"dwarahat",
"bagwalipokher",
"bhanoli",
"bhikiyasain",
"machhor",
"ranikhet",
"lamgara",
"sult",
"someshwar",
"syalde"
]
},
"status_code": 200,
"message_code": "success",
"message": "Success",
"success": true
}