### Check Successful Connection to Root Endpoint using curl

Source: https://github.com/hyperverge/db-verification-india-rest-api/blob/master/README.md

This snippet demonstrates how to check for a successful connection to the root endpoint of the HyperVerge DB Validation API using a GET request. It expects a 'plain/text' response of 'Aok'.

```curl
curl https://ind-verify.hyperverge.co/api
```

--------------------------------

### Authentication using curl with appId and appKey

Source: https://github.com/hyperverge/db-verification-india-rest-api/blob/master/README.md

This snippet shows how to authenticate with the HyperVerge DB Validation API using curl. It includes the appId and appKey in the request header.  The appId and appKey are provided by the HyperVerge team.

```curl
curl -X POST https://ind-verify.hyperverge.co/\
  -H 'appid: xxx' \
  -H 'appkey: yyy' \
  -H 'content-type: application/json;' \
  -d '{}' \
```

--------------------------------

### PAN Name Fetch Success Response Schema

Source: https://github.com/hyperverge/db-verification-india-rest-api/blob/master/README.md

Schema for a successful PAN name fetch response. The response includes the status, status code, and the name of the PAN holder.

```json
{
  "status": "success",
  "statusCode": "200",
  "result": {
    "name": <Name of the PAN Holder>
  }
}
```

--------------------------------

### Verify PAN Success Response Schema

Source: https://github.com/hyperverge/db-verification-india-rest-api/blob/master/README.md

Schema for a successful PAN verification response. The response includes the status of the PAN card, whether it's a duplicate, and if the name and date of birth match.

```json
{
  "status": "success",
  "statusCode": "200",
  "result": {
    "status": "Active",
    "duplicate": false,
    "nameMatch": true,
    "dobMatch": true
  }
}
```

--------------------------------

### PAN Name Fetch Error Response Schema - Invalid Input

Source: https://github.com/hyperverge/db-verification-india-rest-api/blob/master/README.md

Schema for an error response when invalid input is provided for PAN name fetching. The response includes a failure status, a 422 status code, and an error message.

```json
{
  "status": "failure",
  "statusCode": "422",
  "error": "Invalid value passed for an input"
}
```

--------------------------------

### DL Verification Success Response Schema

Source: https://github.com/hyperverge/db-verification-india-rest-api/blob/master/README.md

Schema for a successful DL verification response. The response includes details such as issue date, father/husband name, user name, image, blood group, date of birth, validity, coverage details, and address.

```json
{
  "status": "success",
  "statusCode": "200",
  "result": {
    "issue_date": <Date of issue in DD-MM-YYYY format>,
    "father/husband": <Father Name/Husband Name>,
    "name": <Name of the User>,
    "img": <Base64 image of the user profile photo>,
    "blood_group": <Blood Group of the user>,
    "dob": <Date of Birth in DD-MM-YYYY format>,
    "validity": {
      "non-transport": "Date Range, DD-MM-YYYY to DD-MM-YYYY",
      "transport": ""
    },
    "cov_details": [
      {
        "issue_date": "Date of Issue/Issuing Authority",
        "cov": "Coverage type of license"
      }
    ],
    "address": "Address of the User in the DL"
  }
}
```

--------------------------------

### Common Error Response Schema - Data Source Unavailable

Source: https://github.com/hyperverge/db-verification-india-rest-api/blob/master/README.md

This JSON schema represents a common error response when the data source is unavailable. The status code is 503, and the error message indicates that the data source is not available.

```JSON
{
	    "status": "failure",
	    "statusCode": "503",
	    "error": "Data Source not Available"
	}
```

--------------------------------

### Verify PAN Error Response Schema - PAN Not Found

Source: https://github.com/hyperverge/db-verification-india-rest-api/blob/master/README.md

Schema for an error response when the PAN number is not found in the database. The response includes a failure status, a 422 status code, and an error message.

```json
{
  "status": "failure",
  "statusCode": "422",
  "error": "Entered id is not found in any database"
}
```

--------------------------------

### Verify PAN Error Response Schema - Invalid Input

Source: https://github.com/hyperverge/db-verification-india-rest-api/blob/master/README.md

Schema for an error response when invalid input is provided for PAN verification. The response includes a failure status, a 422 status code, and an error message.

```json
{
  "status": "failure",
  "statusCode": "422",
  "error": "Invalid value passed for an input"
}
```

--------------------------------

### PAN Name Fetch Error Response Schema - PAN Not Found

Source: https://github.com/hyperverge/db-verification-india-rest-api/blob/master/README.md

Schema for an error response when the PAN number is not found in the database during PAN name fetching. The response includes a failure status, a 422 status code, and an error message.

```json
{
  "status": "failure",
  "statusCode": "422",
  "error": "Entered id is not found in any database"
}
```

--------------------------------

### DL Verification Error Response Schema - DL Not Found

Source: https://github.com/hyperverge/db-verification-india-rest-api/blob/master/README.md

Schema for an error response when the DL number is not found in the database. The response includes a failure status, a 422 status code, and an error message.

```json
{
			"status": "failure",
	        "statusCode": "422",
			"error": "Entered id is not found in any database"
		}
```

--------------------------------

### Bank Account Verification Success Response Schema

Source: https://github.com/hyperverge/db-verification-india-rest-api/blob/master/README.md

This JSON schema represents a successful response from the Bank Account Verification API. It includes bank details such as account number, IFSC code, and account holder name.

```JSON
{
     "status": "success",
     "statusCode": "200",
     "result": {
       "bankResponse": "Transaction Successful",
       "ifsc": <IFSC Code>,
       "accountNumber": <Account Number>,
       "accountName": <Name of the Account Holder>,
       "bankTxnStatus": true
     }
  }
```

--------------------------------

### DL Verification Error Response Schema - Invalid Input

Source: https://github.com/hyperverge/db-verification-india-rest-api/blob/master/README.md

Schema for an error response when the DL number and DOB combination is incorrect. The response includes a failure status, a 422 status code, and an error message.

```json
{
			"status": "failure",
	        "statusCode": "422",
			"error": "Invalid value passed for an input"
		}
```

--------------------------------

### Common Error Response Schema - Invalid Input Format

Source: https://github.com/hyperverge/db-verification-india-rest-api/blob/master/README.md

This JSON schema represents a common error response when the input format is incorrect. The status code is 400, and the error object provides details about the error.

```JSON
{
	    "status": "failure",
	    "statusCode": "400",
	    "error": {
	        "code": 1099,
	        "message": <String, message describing the error>,
	        "path": "...",
	        "type": "...",
	        "context": "..."
	   	 }
	}
```

--------------------------------

### Bank Account Verification Failure Response Schema

Source: https://github.com/hyperverge/db-verification-india-rest-api/blob/master/README.md

This JSON schema represents a failure response from the Bank Account Verification API. It indicates that the bank account number is incorrect, with bankTxnStatus set to false.

```JSON
{
	       "status": "success",
           "statusCode": "200",
           "result": {
             "bankResponse": <Failure Reason>,
             "ifsc": <IFSC Code>,
             "accountNumber": <Account Number>,
             "accountName": "",
             "bankTxnStatus": false
         }
       }
```

--------------------------------

### Voter ID Check Success Response Schema

Source: https://github.com/hyperverge/db-verification-india-rest-api/blob/master/README.md

This JSON schema represents a successful response from the Voter ID check API. It includes voter details such as name, address, and EPIC number.

```JSON
{
    "status": "success",
    "statusCode": "200",
    "result": {
        "ps_lat_long": <Latitude and Longitute of Polling Station>,
        "rln_name_v1": <Relation Name 1>,
        "rln_name_v2": <Relation Name 2>,
        "rln_name_v3": <Relation Name 3>,
        "part_no": <Part Number>,
        "rln_type": <Relation Type>,
        "section_no": "Section Number",
        "id": "ID of VoterId Card",
        "epic_no": "EPIC Number",
        "rln_name": "Relation Name",
        "district": "District",
        "last_update": "Last Update Timestamp",
        "state": "State",
        "ac_no": "",
        "house_no": "House Number",
        "ps_name": "Polling Station Name",
        "pc_name": "",
        "slno_inpart": "",
        "name": "Name of the User",
        "part_name": "",
        "dob": "DOB in DD-MM-YYYY Format",
        "gender": "Gender of the User",
        "age": <Age of User, Number>,
        "ac_name": "Account Name",
        "name_v1": "",
        "st_code": "",
        "name_v3": "",
        "name_v2": ""
    }
  }
```

--------------------------------

### Voter ID Check Not Found Error Response Schema

Source: https://github.com/hyperverge/db-verification-india-rest-api/blob/master/README.md

This JSON schema represents an error response when the EPIC number provided for the Voter ID check is not found in the database. The status code is 422.

```JSON
{
			"status": "failure",
	    "statusCode": "422",
			"error": "Entered id is not found in any database"
		}
```

--------------------------------

### Voter ID Check Invalid Input Error Response Schema

Source: https://github.com/hyperverge/db-verification-india-rest-api/blob/master/README.md

This JSON schema represents an error response when the EPIC number provided for the Voter ID check is invalid. The status code is 422.

```JSON
{
			"status": "failure",
	    "statusCode": "422",
			"error": "Invalid value passed for an input"
		}
```

=== COMPLETE CONTENT === This response contains all available snippets from this library. No additional content exists. Do not make further requests.