Instnt provides SDKs in various languages and APIs for your company to utilize throughout your onboarding workflow and a self-serve web dashboard for establishing administrators, provisioning users, and managing your signup workflows.
To begin utilizing Instnt's platform in a testing environment, refer to the following GitHub repositories:
For Instnt's public API endpoints, visit Instnt's dedicated Swagger page.
Understanding Instnt's Platform
The following pages describe in detail the integration requirements and back end functionality of Instnt's platform.
Learn how to encrypt your public/private keypairing and decrypt the assertion response payload in order to fully onboard with Instnt!
You alone, being in possession of the private portion of the keypair, can decrypt this data. These keys are signed via RSASSA-PKCS1-v1_5 SHA256 and encrypted by RSA-OAEP for key wrapping and AES GCM for payload encryption.
Setting trusted domains is an important part of the workflow generation process, so review our Cross-Origin Resource Sharing (CORS) documentation to understand how this function helps secure your workflow.
CORS is an HTTP-header based mechanism that allows a server to indicate any other origins (domain, scheme, or port) than its own from which a browser should permit loading of resources.
The assertion response displays the relevant metrics that determine acceptance, rejection or manual review decisions from the Instnt engine.
It also lists the relevant information for the specific customer tied to it, including: first name, last name, mobile number, email, etc., and data and metadata that was processed about the enrolling user's device, biometric behaviors, geolocation, network cohort analysis, KYC and document verification outcomes.
Resources and Reference Materials
Instnt's API processes field data objects to produce a variety of reason codes. The following pages contain all relevant reference data for Instnt's platform.
This glossary contains information about the field dictionary necessary for integrations where your server-side POSTs to the workflow submission API end-point for workflow processing.
This page contains a list of Reason Codes used by Instnt and their definitions.