• Camera Scanning
  • ID Parsing
  • DIVE
  • Web Services
  • Third Party Checks
  • Authentication
IDScan.net
  • Introduction
  • Getting Started
Search Results for

    Show / Hide Table of Contents
    • Introduction
      • Getting Started
      • Web Library License Key
      • Supported Document Types
      • Recommended Browsers
      • Supported Image File Types
      • Image Requirements
      • Hosting Options
      • Security
      • FAQ
    • DIVE API
      • Web Portal
        • Bearer Tokens
        • License Keys
        • Verification Requests
        • Reviewable Submissions
        • Suspicious Activity Monitoring
        • Settings
      • Integration Options
      • Web Library V2
        • Migration Guide
        • Installation
        • Configuration Settings
        • Functions
        • Event Handlers
        • Style Customizations
      • Additional Verification Services
      • API Manual
      • Overriding Server Settings
      • Verify Use Cases
      • Authentication Use Cases
      • Verification/Authentication Response
      • Error Codes
      • Swagger UI
      • DIVE Web API Demo
    • DIVE Online
      • Web Portal
      • Integration Options
      • Wrapper
        • Installation
        • Configuration Settings
        • Functions
        • Event Handlers
      • SMS
      • Webhooks
      • Callback URLs
      • API Manual
      • Swagger UI
    • Native SDKs
      • iOS SDK
      • Android SDK
      • Sample Apps
    • DIVE Web API Sample Apps
      • Client Side Sample Apps
        • Vanilla Javascript
        • Angular
        • Vue
        • React
        • Svelte
      • Backend Sample Apps
        • Express (Firebase Cloud Function)

    Getting Started

    When building an application using DIVE you will first need to decide whether you will be using the DIVE API or DIVE Online

    DIVE API

    Any DIVE API integration will include the following three components

    1. DIVE Web API
    2. Client Side Application
    3. Backend Application

    The DIVE API integration begins with the client-side application making a request the backend application. The backend then adds the DIVE API secret key to this request and forwards it to the DIVE API for processing. Once the DIVE API processes the request, it sends the response back to the backend application, which in turn returns it to the client-side application that initiated the request. DIVE API Integration

    DIVE Online

    DIVE Online provides the quickest way to begin submitting documents to the DIVE API. On the very same day you get your log in credentials you can start sending SMS/email messages to your end users and having them submit documents for verification. The results would then be reviewable in the DIVE Online Web portal.

    Your end users will receive a message with a link inside that brings them to a web page maintained by IDScan.net. From this page they can upload images of their document to the DIVE Online API. You and your team can save the time and effort of building your own application by using the DIVE Online Web Portal to send out the SMS/email messages and to review the results of each of your end users submissions. The results can also be forwarded via a Webhook to any endpoint you configure. This allows flexibility for customers who may want to customize the DIVE Online solution to better suit their needs.

    DIVE Online SMS Option

    In This Article
    • DIVE API
    • DIVE Online
    Back to top IDScan.net IDScan.net GitHub