How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
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.2.0, 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.2.0
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.

ValidateInput
object
Representative validation body (modeled). Carries user-entered values under userInput and the OCR/QR extraction under ocrResult, ocrResultFront/ocrResultBack,…
5 properties
ValidationResult
object
Representative per-field match response (modeled).
3 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
Where this information came from

This is an independent, third-party profile of HyperVerge Input Validation API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.