HyperVerge Matching API
Fuzzy and direct field matching.
HyperVerge Matching API is one of 6 APIs that HyperVerge publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include Matching. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.
This API exposes 1 operation across 1 path, and defines 2 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.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 1
HyperVerge Matching 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 1
Across 1 path, the API surfaces 1 operation — 1 POST. Each is listed below with its method, path, parameters, and response codes.
Fuzzy and direct field matching.
Schemas 2
The contract defines 2 schemas that model the data the API accepts and returns. The most detailed are Error (3 properties), ValidationResult (3 properties). Each schema is shown below with its type and property counts.
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
More from HyperVerge 5
Other APIs HyperVerge publishes across the network.