Need help with your APIs? I offer API discovery, governance & evangelism services. Explore services →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

HyperVerge Input Validation API

Cross-validation of user input against OCR/QR extraction output.

HyperVerge Input Validation API is one of 6 APIs that HyperVerge publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Input Validation. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 4 operations across 4 paths, and defines 3 schemas. It is described by OpenAPI 3.0.3, at version 1.0.

Requests are made against 3 base URLs: https://ind-verify.hyperverge.co, https://ind-docs.hyperverge.co/v2.0, https://ind-faceid.hyperverge.co.

4 operations 4 paths 3 schemas 4 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.3
API Version
1.0
Base URL
https://ind-docs.hyperverge.co/v2.0
Authentication
API Key
Contact
Resource Areas
1

Authentication & Security 1

HyperVerge Input Validation API declares 1 security scheme for authenticating requests. An API key is passed in the header as appId (appIdKey). By default, every request must be authenticated.

  • appIdKey — HyperVerge issues an appId and appKey pair after enterprise onboarding. Both are sent as request headers: appId and appKey on the ind-docs and ind-verify hosts…

Paths & Operations 4

Across 4 paths, the API surfaces 4 operations — 4 POST. Each is listed below with its method, path, parameters, and response codes.

Input Validation 4

Cross-validation of user input against OCR/QR extraction output.

POST
/api/validatePANInput
Validate PAN input against OCR
validatePANInput body → 200401
POST
/api/validateAadhaarInput
Validate Aadhaar input against OCR/QR
validateAadhaarInput body → 200401
POST
/api/validatePassportInput
Validate passport input against OCR
validatePassportInput body → 200401
POST
/api/validateVoterIdInput
Validate Voter ID input against OCR
validateVoterIdInput body → 200401

Schemas 3

The contract defines 3 schemas that model the data the API accepts and returns. The most detailed are ValidateInput (5 properties), Error (3 properties), ValidationResult (3 properties). Each schema is shown below with its type and property counts.

ValidationResult
object
Representative per-field match response (modeled).
3 properties
ValidateInput
object
Representative validation body (modeled). Carries user-entered values under userInput and the OCR/QR extraction under ocrResult, ocrResultFront/ocrResultBack,…
5 properties
Error
object
3 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

hyperverge-input-validation-api-openapi.yml Raw ↑

Other APIs HyperVerge publishes across the network.

HyperVerge Liveness Detection
HyperVerge Database Verification API
HyperVerge Face Match API
HyperVerge KYC OCR API
HyperVerge Matching API