The /start API allows you to choose Signals for ID verification. Specify them in the /start signals parameter.

The following table describes each of the available signals. In the table:

The Developer Signal Name column shows the signal name as required in the signals array of the /start request.
The Feature Name column shows how the developer signal name is referenced on the Intellicheck website and in product literature. For example, ocr_match is the developer signal name, while Doc Verify is the equivalent feature.

Developer Signal Name	Feature Name	Description
`idcheck`	Authoritative North America Barcode	Verify US, US territory and Canadian-issued IDs with a DMV-issued barcode using unique and accurate analysis of hidden security data in DL/IDs.
`ocr_scan`	International Verify	Expand your reach with global ID support. Accept passports and international IDs as part of your identity verification process—ideal for travelers and users without local credentials.
`ocr_match`	Doc Verify	Enhance document trust by using advanced machine learning to convert scanned images into structured, machine-readable data. It automatically compares the printed information on the front of the document with the data encoded in the verified DMV-issued ID, ensuring consistency, accuracy, and reliability. This powerful verification process gives organizations greater confidence in the authenticity of every document.
`selfie`	Face Verify	Increase identity verification security and accuracy using a biometric selfie to confirm the authenticity of the ID while matching the face of the person submitting it. Face Verify uses the DMV-issued ID and a real-time selfie to detect likeness and liveness with high accuracy to help prevent AI deepfake impersonation and synthetic identity use.
`document_liveness_idrnd`	Doc Liveness	Add a powerful layer of protection by verifying that the image captured by the user’s phone is of a live, physical identity document—not a photo of a screen or a printed copy. It also analyzes the portrait on the front of the ID for signs of tampering or manipulation.

Signal Selection

To selectively apply signals in the /start endpoint, you use the signals parameter in the request body. If you do not provide these parameters, all data for signals to which your company account is subscribed will be returned.

For example, the following /start private_data request body could be used for the International Verify signal to validate a passport booklet (ocr_scan) and the Doc Verify signal to return OCR match results (ocr_match).

{  
  "private_data": {
    "document_type": "passport",
    "signals": [  
      "ocr_match",  
      "ocr_scan"  
    ],      
  }  
}

To additionally obtain the results of the Face Verify signal (selfie), the /start private_data request body might look like this.

{  
  "private_data": {
    "document_type": "passport",
    "signals": [  
      "ocr_match",  
      "ocr_scan",
      "selfie"
    ],      
  }  
}