Integration Overview
The IDV Platform exposes everything through a small set of well-defined surfaces. An integration typically uses two of them: one to run verification workflows, one to manage records.
The surfaces
| Surface | Purpose | Who calls it |
|---|---|---|
| Capture & Workflow API | Start and drive the capture for a verification session; receive the result. | The Company's backend + the capture front-end. |
| Customer API | Read, search, update, and transition Customer and Digital Identity records. | The Company's backend. |
| Mobile Capture SDK | Development of native apps on Android & iOS. | The Company's mobile app. |
| Web Components | Development of web-based applications. | The Company's website. |
| Website Redirect | Performing the workflow by redirect to an Innovatrics' hosted web. | The Company's website. |
| No-code | Email response as a replacement of integration. | Fast-start integrations. |
| Webhooks | Callback notifications for results and events. | Delivered to the Company's backend. |
How they fit together
- The Company's backend starts a session by choosing a workflow.
- The app or website runs the capture steps (via SDK or web components) and submits data.
- All biometric processing runs server-side; the result comes back to the backend synchronously or via webhook.
- Afterwards, the backend uses the Customer API to read history, correct data, or drive state changes.
Authentication
- The Capture & Workflow API and Customer API authenticate with OAuth2, that are obtained in the Configuration > Integration settings . Token exchange must happen on the Company's backend, never on the client device, to protect credentials.
- Webhook deliveries are signed so the receiver can verify authenticity.