DocVer integration tutorial

The tutorial on integration provides a sample of how to configure the environment, set up verification, integrate the client component, and utilize the API.

Basic concepts and terms we are using

An Applicant is a person or entity that requires verification.

Verification can include checks such as KYC or AML, which may require documents such as a passport and a photo of the applicant.

Verification is the process of checking an applicant's identity and other relevant information. This may include verifying documents and other information provided by the applicant.

A Verification profile is a set of settings that determine how verification will be conducted, what checks will be performed, and any other customizations.

A Public link is associated with a verification profile and allows any applicant to initiate verification using that profile.

HTTP API and SDK

The HTTP API enables users to manage verification, applications, accounts, verification profiles, and other settings and entities.

Explore our API documentation here https://docs.dataspike.io/api.

Use any HTTP Client library that enables you to utilize the HTTP API.

Currently, we support SDKs for programming languages such as Python and Go. All SDKs are open-source projects.

Python SDK

For Python, the official package is called dataspike PyPi. Install it to get started. Check out the PyPi or GitHub README to learn how to get started with it.

Golang SDK

For Go, install it with go get github.com/dataspike-io/docver-sdk-go. More information at Github project README.

Web SDK

With our WebSDK, you can seamlessly integrate our powerful features into your web-based applications.

WebSDK located at https://github.com/dataspike-io/docver-widget More information look at docver widget github page or short guide here